Dart let's me focus on the app I'm writing, the data structures, the business logic & the overall architecture as well as value is I'm providing to my customers without getting held up with heisen-bugs.
This has a lot to do with getting into the zone/flow. I personally don't want to run into things like language insanities while I code, I also don't want to accumulate a huge repository of patterns or workarounds to avoid the bad parts/minefields of a language.
I wonder where the "It's the worst parts of Java brought into Javascript" FUD is coming from.
As I see it Dart avoids the worst parts of Java (http://www.javapuzzlers.com/) and JavaScript (https://www.destroyallsoftware.com/talks/wat) and mixes it up with great parts borrowed from various languages and platforms (mixins, streams, async/await, …).
Dart is a dynamic language at heart, yet provides great performance (even faster than JavaScript which by now has pretty fast implementations in the wild compared to ruby/python): https://www.dartlang.org/performance/
If you are used to tooling support (autocompletion, warnings/hints, code navigation like in Java/Scala/C#) on a level which traditionally only statically typed platforms offered you also get it with Dart (see support for IntelliJ/Webstorm: https://www.dartlang.org/tools/webstorm/ & Sublime: https://github.com/dart-lang/dart-sublime-bundle).
So I don't really understand where the "worst parts of Java brought into JavaScript" sentiment comes from. I'd like some concrete examples.
I'm not a javascript fan by itself, but I do like coffeescript. I was probably making a comparison in my mind of coffeescript vs dart?
I prefer more heavy-weight approaches that use Javascript as a compilation target. Clojure and Scala can both compile to Javascript, but you're talking about different communities, libraries and tools, so very much like Dart, but focused on targeting just Javascript VMs.
JavaScript => CoffeeScript => Dart.
I think once you've took the red pill of "There has to be something which is better than JavaScript" it is hard to go back.
Once you've written some CoffeeScript you will start to long for even more semantic improvements beyond classes, preventing you from polluting the global namespace and being able to bind `this` using the fat arrow.