Javascript Fatigue
Eric Clemmons
1.5K93
The main problem is that things are moving so fast — best practices change every month as someone comes out with a new approach to a problem. Now we have isomorphic JS (which is in its infancy) — how do we handle that? There’s a whole slew of tools that can come from researching that paradigm. Tools like Babel completely refactor their APIs, so you have to edit scripts to make sure you’re getting the latest updates.
I think the JavaScript ecosystem is still very unstable, and it is why we haven’t seen opinionated frameworks becoming commonplace and wanted. Sure, someone can create a redux/react-based opinionated front end framework, but it’ll probably be obsolete in 3 months. Such is JavaScript vs, say, Rails.