The Death of Dart
The year is 2015...
To improve JS development within a framework, things such as Typescript and ES6 (Harmony) have emerged. This is also great.
Sadly, development of Dart has recently taken a huge turn. Don't get me wrong, I think their decision was the right one. In case you missed out, the Dart team has decided to stop focusing on the integrating the VM into chrome and instead focusing their efforts else where.
Now, there's a good reason that I'm not the man who writes the obituaries around here, but I'm going to go ahead and call it. Dart is dying. This is bad.
Let's shine some light on what Dart has done for us. Dart has been able to provide us with the first real structured language that was able to be used on the frontend (until ES6, JS wasn't well structured in my opinion). It also allowed backend developers to somewhat-comfortably handle frontend development. Most importantly, however, is that its half the reason ES6 and Typescript are where they are today.
Dart's death isn't going without purpose. It's lived a life similar to the hero that dies young, but ends up saving the world. Our world of frontend development will be forever better due to the standards it has set in place, but it won't live much longer.
Why must the good die young?
Dart, you've spawned a revolution, but you didn't live up to my dreams.