It's in vogue to hate the Javascript community right now - especially if you're part of it. If you spend any time on Hacker News you've likely seen a consistent stream of new Javascript frameworks, libraries and build systems cross your screen, each of which attracts tens or hundreds of comments saying "no more!"

You've also seen claims of "Javascript Fatigue" from developers diving into those discussion threads, deriding the "treadmill" that the language and ecosystem has become, complaining of how keeping up is "a struggle."

Even within library-specific enclaves of the Javascript world things are falling apart. Developers were outraged when Angular 2 broke compatibility with Angular 1. Claims of how disruptive migrating to 2.0 would be to teams and development alike were everywhere. Developers felt betrayed after investing years into learning one way of doing things, only to be forced to throw it all away and learn something totally different.

The Javascript world is turning into a fractal of frustration and derision, driven by developer exhaustion.

This is Madness

It's not your (and I assume you're a developer, if you're reading this) job to keep your codebase up-to-date with the latest and greatest Javascript techniques. Your Angular 1.x code didn't suddenly stop working because Facebook launched React. Your Browserify config didn't spontaneously combust because Webpack made #1 on Hacker News. If you have a teamful of people trained on Ember or TypeScript, it doesn't make sense to transition them over to React or Elm.

As a developer, your first duty is to the customer, your second duty is to the product and your third is to your team. Choice of language or library isn't even in the top 3. Use what works, use what you know. It's not going to crumble in your hands just because something new came along.

Opt Out of Javascript Fatigue

Product managers, customers, CxOs, none of them care about the hottest Javascript tech. If yours do, you should start running. If you're exhausted by it, get off the treadmill for a bit. Focus on your chosen stack. Train your team on your chosen libraries. Leave your FOMO at home. Build something amazing.

Afraid of getting left behind?

Don't be.

It'll all be there when you get back.

The Hacker News posts, the Medium essays. Even the posts on <your favourite startup>'s engineering blog.

You might have missed a few libs that blew up, got big and then just as quickly died.

Who cares? You made something. Now you can take a moment to learn about the Next Big Thing... if you want. Or you could just make another cool thing with the stack you know.

Opt out of Javascript fatigue. Opt in to making cool stuff.

1 Comment