The state of JavaScript

Breaking my “no tech posts” habit, Jimmy Breck-McKye has a notable article about on the state of JavaScript in 2015:

Innovation is great, but this kind of churn rate seems excessive. It’s just not possible for developers to make large, upfront investments of time in getting to grips with new frameworks and technologies when there’s no guarantee of their longevity. Programmers want to program – they want to build things, and be masters of their craft. But how can we get anything done when we’re spending most of our time learning? How can we feel like craftsmen when we’re scrabbling in the dark with unfamilar tech?

[…]

  • The churn rate of front end JavaScript technologies is problematic
  • People are starting to feel burned out and alienated by the pace of change
  • The answer might be to eschew monolithic frameworks in favour of microlibraries

I was feeling burned out by this explosion of technologies last year. I don’t think the landscape has got any better since then; in fact, the Angular 2.0 roadmap has probably forced more people to confront the situation.