This is huge. Finalization of the module loader spec is usually what's cited as the last remaining blocker for full implementation of modules in V8 [1]. Combined with HTTP2 being available nearly everywhere [2] and native ES6 support soon reaching most mainstream browsers [3], it means that web developers will soon be able to drop a large portion of the current JS stack, including spriting, Webpack, and Babel.
Re [3]: Nice, it seems that both Blink and Webkit are nearing 100% support for ES6. Safari Technology Preview already has 98%, so next major version of Safari (presumably both on desktop and on mobile) will have it too. So this autumn we can expect to have ES6 in every browser that matters!
Node 6.0 is also supposed to come out in late April [1], targeting v8 5.0, which IIRC corresponds to Chrome 50 on the compatibility table. Not quite as nice as the Chrome 52 release, but still covers most of the ES6 features I actually use.
FF48 and Edge 14 don't do so badly either. If you drill down into their missing test cases, it's largely features that few people care about.
Note that this table doesn't test all parts of ES6, obviously. It's not that hard to have a feature listed as "supported" in this table while not actually following the spec very well at all.
In practice, browsers usually try to not do that sort of thing, of course. But note the double-caveat there. ;)
> So this autumn we can expect to have ES6 in every browser that matters!
I wish I could afford to ignore Internet Explorer... if Microsoft leaves Windows 7 to rot with IE 11, corporate users are going to keep holding back the web for a few more years.
[1] https://bugs.chromium.org/p/v8/issues/detail?id=1569
[2] http://caniuse.com/#search=http2
[3] https://kangax.github.io/compat-table/es6/