Recently, I attended a developer conference that discussed Dart by Google. Dart is a relatively new language from Google designed for modern desktop and mobile browsers. The idea behind Dart was to create a language that could replace Javascript with something more structured and object oriented – similar in the same spirit as other tools such as Closure or CoffeeScript. Javascript is the standard for client-side web development, and many platform advances work to support Javascript, not move away from it. Not that Javascript is all bad, but large programs written in Javascript can easily become difficult to maintain.
First off, the presenter cautioned that Dart needs “modern browsers” to be effective. The gist of it was that if your browser doesn’t support HTML5 (IE9+ or recent versions of Firefox/Chrome) it probably won’t work. This is almost certainly a showstopper for many organizations that might want to try Dart. That said, it certainly seems like an interesting technology if you can dictate which browsers will be used (e.g., for an intranet application) or for future use when HTML5 support is a given. Essentially, Dart takes everything the Java/C# developer expects now for developing server side code – a nice IDE, classes, libraries, projects for managing source files, familiar syntax – and lets you use that to build client side apps. These can then be compiled into Javascript, or run natively on the browser in the Dart VM (largely theoretical at this point as no production browser actually has a Dart VM)
Some highlights that I gathered from this session, included:
- Syntax is very similar to Java or C#, easy to understand and pick up.
- Can be either statically or dynamically typed, or both at the same time. Types are optional.
- Has its own IDE (basically a stripped down customized version of eclipse) with all kinds of nice things you would expect in visual studio, but could only dream about in Javascript
- Has built in templating support for creating more semantic HTML with databinding – similar to MVVM and XAML in WPF. This looked very cool.
While Dart is certainly interesting, it does not seem that Chrome will take over the browser world anytime soon, and with the fact that platforms are trying to accommodate the intricacies of Javascript, it does not seem that a shift to Dart is necessarily a benefit at this time.

But what if you could engage your TV and were encouraged with Games? It would revolutionize the way we currently watch TV. Venu gave his opinion on what works and what doesn’t, explaining that gaming only works when you take it a step further than badges and leader boards. When gaming truly works, a ‘rewards’ structure must consist of Intrinsic Motivation.