Earlier quoted context omitted.
I don't think the predicted lack of support for a Dart VM outside of Chrome is a significant factor – a strength of the linked video was that it focused on Dart-delivered-as-JS. > I don't see how using jQuery to create a button is any more "routing around the problem" of DOM creation than using Dart's framework, when they are both translated to document.createElement. With Dart, you don't need to send 96k of jQuery o…
With Dart you need to send the Dart framework over the wire. That's my point, you've replaced the flexibility of sending the framework(s) you want/need and haven't gained anything. Sure, the Dart framework is smaller, but it also does less. If you don't need everything that comes with jQuery, you can swap it out for something smaller, like zepto or TinyDOM - which make Dart look massive. jQuery, zepto, xyz, abc, ...…
Take the button creation example.
With jQuery you have to use an odd syntax, IMO, and it requires the whole jQuery library to be downloaded:
var button = $('');
var button = new ButtonElement();
var button = document.createElement('button');