Organized by the Google Technology User Group Berlin, the event was split in two parts:
- Get a feel of Dart: syntax and sugar for it, trying out the language, samples and the editor
- A rather lengthy presentation by Florian Loitsch (engineer in the core Dart team) with an overview of the language and its features to convince us of the greatness of Dart.
Pros for Dart
Dart seems like a mix of nowadays favorite programming languages, including Ruby, CoffeeScript, Scala and Googles beloved Java.
- Optionalally strictly typed, so instead of
var name = "Reiner"you can write
String name = "Reiner"
- Clean syntax including shorthands for constructors, lambdas, string substitution etc. (resembles Ruby)
- (non-prototypal) Classes, Interfaces (comparable to CoffeeScript)
finalvariables, lists with specfied content-types, e.g.
List<String> names = new List<String>()(resembles Java)
- Performance improvements
varis often unclear until the program is run.)
Reasons against Dart
- Dart needs it’s own VM to compile and run the
.dart-files. There is a dart2js compiler, but you loose at least the performance improvements with it. Google aims to convince the WebKit-Team to integrate a Dart-VM into WebKit, but I think that’s quite a long shot and does not solve the problem for other browsers like Firefox and IE.
Currently, I do not see Dart as the next big hit from Google.
Darts future still is open and it might improve web development, but can also be a fail like Google Wave.