Echo JS 0.11.0

I can't disagree more with the presumptions that are made in the description that Make is easier than JS to understand.  Make requires other build tools to be installed, and depending on the environment that is complicated, if you're in a more locked down windows environment, it's downright difficult.

Not to mention that I don't like the idea of bringing in tools you don't have to.  More often than not lately, I don't use grunt/gulp or the like, simple npm scripts out of package.json, and if I need more, I add them to a `//scripts` directory and call them via npm.

Interesting, but being that the heavy lifting is generally done in actions, not sure how much benefit there is to this, vs. the message brokering (serialization/deserialization)... haven't looked at the code/implementation though.

Interesting, and definitely a nice effort.  If I had a really simple UI need for a quick form or something, would probably reach for this... though if I wanted something more complex, might still reach for the likes of electron.

Missing an example of an action/reducer for clicking the checkbox, and how to handle that with the immutable data structure.

Doesn't indicate that you can, or how to send a given response code 410, 404, 400, etc for a given request.

Kind of wish auth0-lite was in github... Would also be interesting to get a followup Q&A on his impressions in using React, and iirc Redux.

I do find it interesting how much he's leveraging AWS' services, and Lambda in particular.  Also, given that he's using go, curious if the startup for lambda is reduced, and by how much.  I'd be more interested in seeing what steps Amazon is taking to improve Lambda startup time, for better scaling.

I had to learn about NgZone while trying to wire up ng2's router with a redux store.  It worked okay, but wasn't entirely happy with it...

Not sure that I like monkey patching require quite like this... and tbh if you're using babel (for any number of reasons, even on the latest node), then you can already get encapsulation with "use strict";

It's funny, that when Apple announced the JS Automation APIs, I didn't quite understand why it wasn't an npm/node module in the first place... other than NIH for the engine.

It's relevant because code style, and project structure are as important as raw performance, especially given, that most applications don't need absolute responsiveness, or 500+ constantly updating fields/components from a feed.