You can't diff between 2.47 and 2.48 and see what changed? Or is that a binary part you don't have source access to?

"Showing 930 changed files with 13,029 additions and 10,187 deletions. "

Feel free to try: https://github.com/SeleniumHQ/selenium/compare/selenium-2.47...

It's a dependency of a dependency with multiple language versions in the one repository.

Rust has plans for a `become` operator for tail call optimization.

Because there's no version control that way. If I depended upon babel/babel (or whatever it's called on Github), when it changed from v5.x to v6.x, it would have broken my build.

You can ask for a specific tag/branch using Github dependencies using babel/babel#v5.x

On Linux, it's 30ish lines, with half of those there to make false.c able to reuse some code. (I know, it's stupid.)

In OpenBSD, it's 3 LoC IIRC.

On at least one OS I worked with, it was 0 bytes long because /bin/sh on an empty file returns true. (I think that was IRIX 4.x.) OTOH, that's slower than the executable from a 3 LoC do-nothing program.

JavaScript doesn't have XSS. The DOM allows for XSS vulnerabilities, but that's an API, not the language.

The author really likes lesbians - see her twitter feed for example. You can safely ignore the 'and gay' part as just a bit of her personality coming out in her artwork as far as the technical argument goes.

Lowest common denominator says to default to ES5, tell people that's the default, and then show them how to change it later if they want or need to.

That's because the core of OO (message passing to opaque things) is really all you can do if you have a PID. In other more-traditional object-oriented languages, they usually have defaults that let you do more than just send messages - such as mutate the internal state directly in ways that the object cannot detect.

If you're talking about a good type system, sure. The type system in Go is frankly terrible at describing the kinds of invariants and reuse we care about.

I'd dare say that diaylizer (Elixir's optional but easy to use type system) would lead to more maintainable code than Go's forced type system in the long run.

That more or less sums up my view on Go in a nutshell.

A compiler takes a text from one language and translate it into text of another executable language.