This session from I/O by Kasper Lund and Lars Bak is well worth a watch: https://developers.google.com/events/io/sessions/324431687
In it they explain that they've pretty much reached the peak of where they can get to in terms of performance with V8 (no more big jumps in performance), but by designing a language that is easier to optimize for, they've already made the Dart VM faster.
It was a process to stop worrying and love the bomb -- so many HN articles proselytizing and condemning Coffeescript (and others) -- but I believe the healing started with the sheer popularity of Coffeescript, and then normalized when Brendan Eich stood on stage with Jeremy Ashkenas and told everyone that compiling to Javascript was A-OK in his book.
So thinking of these languages in those terms is the reason I don't really care about the horse race and I'm ok with people writing in Dart if they want to. My domain will be fine, and might be improved as they find interesting things (syntax, developer tools, whatever) exploring a slightly different path toward a web scripting language.
(though I'll continue to be annoyed if some article on web technology puts all its examples in X where X is not Javascript :)
I agree with you on Typescript, though I don't see it as any more interesting than Closure Compiler annotations plus one of the various ES6 transpilers. It's nice to have those in one package, but I don't really use or want the transpilers normally, so I feel no draw to them now.
As for Dart, I've never totally understood its intended place and how it was expected to succeed there (though we'll see, I guess), but as for its use in practice, philosophically I now just think of it as another Coffeescript, and so I'm at peace with the idea that people want to use it.