Dart doesn't really need "frameworks" in the way that JavaScript does. The core libraries are very rich: * dart:async give you Futures (Promises in JS, no ne

Dart doesn't really need "frameworks" in the way that JavaScript does. The core libraries are very rich: * dart:async give you Futures (Promises in JS, no need for Q) and Streams * dart:core and dart:collections give you real data structures like List, Map, Set, Queue, LinkedList, LinkedHashMap, etc. Much more comprehensive than underscore.js * dart:html is much improved over JS's DOM, and have most of jQuery's functionality (see ElementList). * New and upcoming standards like Shadow DOM, custom elements and template binding let you declaratively define your HTML template in HTML with data-binding, which is the foundation of frameworks like Ember, Angular, Knockout, etc. * Polymer is a JS and Dart library for helping you write custom elements. Also, the package system in Dart, pub, is very similar to npm and encourages smaller, focused packages rather than sprawling frameworks. Check it out, it's a very nice language and environment. But I'm on the Dart team, so I'm obviously biased.