Echo JS 0.11.0

I think it's time to start migrating for any 1.x holdouts (myself included).

I am... Though even that is getting there, and iirc webpack2 does es6 modules directly.

Very nice deck outlining some performance improvements for recent v8 versions... will really be nice to see node@8 with all the new shiny features... async/await is about the last thing I'm using babel for on the server side.

Yeah, I tried to use tape at first, but it was just too slow.. about 5x as slow as mocha, and that's without any actual tests in place.  Right now all it does is hit the main test which loads all the js files (force coverage), all the others are empty... tape/tap took like 30+ seconds, compared to about 2 with mocha.  Haven't touched jest though.

Not so much going for code splitting as separating the latest FF/Chrome (maybe edge) from the rest... since most of ES2015-2016 is supported in the browser, no need to transpile those features.  So the bundle size can be quite a bit smaller.

One more thing I'm doing with the final output is building with preact instead of react, though may revert that in practice, since preact uses real-dom, which may be too slow for some use cases.

Thanks... I wanted to try and create a clean starting structure.  Though it's a bit more verbose than many, and I've opted for my own scripts over gulp or similar, I find it makes it easier to figure out what's going on when you need to... I still have a bit to finish up, then will probably attempt to move to webpack2 as a step towards a dual-output for dist/.

the dist/ output has everything needed to run, translated/built with a more minimal package.json, and the tests are configured with 100% requirements with pretest and load checking to ensure all files are tested.  Although I haven't really written any tests yet, it's been in a making it all work phase.

To this day one of my biggest niggles with jQuery is events use the context for the item the event handler is bound to... you can't use fat-arrow functions with jQuery events.

Probably the nicest JS formatter I've seen, period, I usually disable auto formatting, mainly because they just mangle my clean code too much.

I replied directly into the article, but one thing bugs me... the two demarkations for ng2+ being "Component structure" and "typescript" are both possible with React.  Though I don't care much for typing, it's an option.

Beyond this, I feel the statement that React doesn't match the ecosystem of Angular disingenuous at best at this point.  React works with the rest of the js/npm ecosystem, with far more third party component options today, let alone regular js modules beyond react.

I can't help but think this will be incredibly awesome and horrible at the same time.  My biggest hope is this will allow for DRM to be removed from the browser itself and used via WebAssembly where necessary.

However, I also feel sad, because I can see a rise of *language to wasm compilers and the resulting limitations of discovery.  One of the greatest things about the web has been the ability to deconstruct what JS is doing... even minified is still more understandable that wasm will be fore most.

Interesting... I've just been doing a babel transform directly[0] for the server-side code.

[0] https://github.com/tracker1/react-redux-materialui-boilerplate/blob/master/scripts/build-server.js