Echo JS 0.11.0

I think the only real gotcha that catches me frequently is "className"...  The rest, not so much.  Also starting to like JSS as well.  It's just such a natural fit, even if it feels much more verbose.

JSX does feel much more like HTML + JS to me than any templating library ever has.  From handlebars/mustache to angular, to vue, to whatever else.  JSX is a realization I'd been hoping for since first working with E4X (which never gained adoption outside moz), it was just a nice way to work with things, and imho JSX is better still.

Disagree with Angular as "Better fit for enterprise-grade applications than React" ... If you want typescript, you can use it with React.  As for anything else, Angular gets in your way far more often than it helps with its' prescriptive patterns.

Okay, that is just cool as all hell...

Even when using gulp, browserify, webpack, etc, I still recommend that people setup their actual task list in package.json so it's more consistently discoverable.

I think it might have been better to specify npm tasks in package.json, then have the pom.xml reference `npm run build` etc, instead of gulp directly.  This could emphasize the separation of the node/js world to the app and beyond this, it would allow the client portion of the project to work as so many other projects do in the client-side space today.

Shouts to @nodeaz and the #gulpjs guys.

I've gotten into pushing my eslint and babel configs into package.json ... I know it bloats it a bit, but then there's one non-hidden file to edit.

Also, env already includes the es2015 bits, so don't need them as a separate module.. just env + anything that isn't in the spec yet.

Easy State doesn't seem to mention no IE support.

No IE10-11 support should probably be spelled out on the homepage (per your observable dependency)... as many will be severely surprised when they find that out.

Sigh, another entities library in npm...

How does this perform with *very* large state trees and modifying smaller points?  It seems to me that the performance for comparing changes, or tracking changes would either mean a lot more memory usage, or be significantly slower with very large state trees.

I'm definitely glad they decided to delay, looking forward as what's in channel for the V8 changes it absolutely makes more since going this route.  Especially how long some organizations have been holding on to older node versions without updating their codebases.

I'm also more than happy to see as many ES features enabled in the box and less need for babel as a build step for server-side code (though it isn't going anywhere for a while).