News for hackers. Stuff that matters.
Re:Ask HN: Dart's Future by spankalee on Friday November 21, 2014 @11:26AM (#8641925)
I fail at HN formatting - I forgot lists were pre-formatted and that horizontal scrolling is annoying. Here's those points again:

- Dart is very toolable and has a great IDE experience in a number of IDEs already: IntelliJ/WebStorm, Eclipse, the Dart Editor, Sublime, etc.

- The semantics are much more sane and predictable than JavaScript: objects are closed; Dart has class-based inheritance with interfaces and mixins; type coercion is eliminated and thus predictable; arrays are real arrays, bound checked and can't have holes; 'this' is lexically bound; accessing a undefined property throws an exception rather than propagating undefined through your program; there are no top-level statements, so startup is predictable; and on and on...

- Dart's syntax combined with interfaces allow for really great libraries, and Dart's core libraries and dart:html take full advantage of that. [] is separate from property access, so Lists, Maps, and Sets have nice-to-use interfaces. There can be multiple implementations of List, Map, etc. It's possible to write delegate/wrapper/proxy classes, etc. Dart's core libraries are a joy to use.

- Static type warnings and checked mode helps developers write correct programs. Type checks really do find errors early and save users time. We see this internally.

There are no comments on this comment yet.