Echo JS 0.11.0

Nice multi-level router... one nit, don't see redux integration, or event handling in the linked page, will have to look into it.  Although redux isn't the only backing solution for react, at this point it's the defacto default.

Oh, I've known quite a few who resisted change... hell, converting ASP.Net apps to use node tools as part of build scripts over the hacky VS plugins was a fight a few years ago... (around node 0.10 release).  There are a lot of old timers that resist change, but I've seen relatively young devs (mid 20's) resistant to change as well.  I don't think it's really a product of age so much as hitting a point where learning new stuff isn't as appealing.

One issue, you don't want your git credentials, or even an auth token... inside your code repo.  raised an issue.

As a relative old-timer, I'm pretty offended by a lot of what you're saying... there are plenty of us who've kept up with the language and techniques (following node from the start, using it actively sine 0.8/0.10), and understand the newer ESnext bits... Been using babel since the beginning, though I was a little late to webpack, wasn't sold on its' value over Browserify.  Fighting for 3+ months in my team to get the tooling updated wasn't fun to say the least.

Beyond that, I was more functionally minded all along, even with C# I was more inclined to have simple POCO with static utility libraries.

Not all of us old timers are out of touch with the times.  That said, web dev is a completely different way of having to think than desktop apps... not to mention cookies vs local/sessionStorage vs indexdb vs websql and where/how it works... Though it's all *FAR* more easy to work with today vs. the turn of the millenium when v4 browsers were kings, and the next-get half baked was just coming out.  I don't think the author of the question would have handled that time at all.

It's clickbait, plain and simple (what do you want from dzone, king of interaction spam for devs). also, most of the functionality of AJAX came from the browser DOM, not the language.

I know I'm beating a dead horse... that said, I never cared for ng1's DI, as it is the opposite of discoverable... ng2 is better, but still kind of broken in terms of controls in templates vs. variables and file names... vs. React where the control matches the variable name, and the import/require references the file... you can discover where things are and/or come from.

Definitely interested in playing with PouchDB, there's also a server implementation that exposes the Couch api interfaces.  I am a bit curious about security... I'm interested in implementing some syncing of user settings to a private db server-side, and authentication is the only thing I'm not nearly familiar enough with.

Will need to find time to look into the PouchDB server implementation to see how security is, or can be implemented.

dupe

I happen to like JS, more so with the extra ES6+ niceties, but I can see the appeal of a more purely functional language without some of the extras.

And no, imho no solution is perfect.. tbh, if it's public facing I'd just prepopulate the store server-side with the essential portion of data and let the rest populate client-side... that would take care of the non logged in user case, and account for search engines... the rest can run client side.  In the end, it's up to the author.

I also happen to really like react in general, and if full server rendering were desired, I'd go the redux-universal route.  I usually use the thunk methods with async functions anyhow, so that allows promise resolution to work in that way.

To each their own though.

Classes in JS(ES6) are definitely sugar over the prototype chain... beyond this, you'll still need to have that inheritance chain for certain contexts.  If you choose prototype syntax over class syntax is entirely subjective.  I happen to think the class syntax is cleaner to look at and follow.

I don't think classical inheritance is a good use case for many types of workflows, for others, they are.  In general, where you want to persist state in conjunction with workflows, classes tend to work better.  Not that you can't work around them, but it really depends on your needs.

I tend to use classes very sparingly in JS.