Google Dart, or ‘how we lost the ECMAScript 4 battle so we decided to create our own language instead’.

So what do you do if you lose a public battle to change the face of JavaScript?

If you're Google, you decide to go it alone, implement what you want to anyway, and then tell the world that it is going to replace JavaScript.

What's the problem with Dart? Apart from the fact that it looks like a Java developer's wet dream and will possibly mean the existence of two client-side programming languages for the web, thereby confusing the heck out of anyone just coming into web programming, it's a solution for problems that mostly Google has. How many folks out there are creating Gmail or Google Docs? And what are the costs of the additional complexity of a language like Dart for people who aren't creating Gmail and Google Docs (in other words, the majority of the web?) And, instead of throwing your toys, flashing the middle finger at the rest of the web community, and going it alone, maybe the thing to do–if you believe in an open and standards-based web–is to play nice with the other kids.

Heck, can you imagine what the fallout would be if Microsoft declared, ‘you know what, we've decided that C# should be the language of the web. Today we're declaring that it's going to replace JavaScript and that every browser should implement it. We're going to start with IE10.’

Remember a time when you thought Google was good? Because it's beginning to look like the playground bully to me. Personally, I hope that no one apart from Google gives Dart–that convoluted and unnecessary ECMAScript 4++ of a language–any notice whatsoever. And here's hoping Google realize their folly before they bloat my favorite browser (Chrome) with that shite.