[cantlin]

I found this enticing in a way that my previous glimpses of Dart haven't been. Summary for the video-averse (conclusion begins at 38:03[0]):

  – Dead code can be eliminated.
  – A little typing goes a long way.
  – The DOM doesn't have to suck.
  – Built-in syntax, your semantics.
  – Classes for stating intent and good tools.
  – Don't be evil: compile to Javascript.

For me the notion of swapping out existing client code compilation steps with a Dart compilation step might almost be worth it just for a legible, declarative class syntax. Throw in a vastly improved DOM API and some sensible syntax choices (e.g. same form for calling a getter as accessing a field, avoiding getFoo() boilerplate) and I'm half way to having a play.

[0] http://www.youtube.com/watch?v=9RCuW6K1afs#t=38:04

[MatthewPhillips]

JavaScript supports getters too.

https://developer.mozilla.org/en/JavaScript/Reference/Operat... https://developer.mozilla.org/en/JavaScript/Reference/Global...

[WayneDB]

Every browser doesn't support them though. The nice thing about a language compiled to Javascript is that you don't have to write any code to check if you can use getters.