Didn't dig into the article, but will say in a test app I wrote a few months ago with ng2, the routing was particularly painful, getting it working with redux (syncing routing info to the state) was more painful still. And the biggest gotcha that you could only pass a route to a child one layer down, couldn't nest routes more than two layers deep.
All told, I really didn't care for ng2 as much as React+Redux, but it's definitely a step up from ng1.
All things considered not very informative of a post, but given a lot of posts targeted at beginners, it's not bad.
Personally, I think that async/await is just about the ultimate transparent use of promises.
It comes down to very different needs, and the composite fit... What would be more cool would be some kind of React Native-like binding that leverages libui under the covers... No idea if/how hard it is to develop/design custom controls against libui though.
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.
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.