Let's face it, the JavaScript ecosystem can be overwhelming.
New libraries appear all the time, there are dozens of libraries to do the same thing. How many date pickers can there be? 10, 20, 50? Keeping up with all the changes seems almost impossible. That is JavaScript fatigue.
If you want to avoid JS fatigue, remember that you don't have to learn everything. I think it's enough just to be aware of the new tools, what their use cases are, and their pros/cons.
With that information, the next time you create a new project and you have to decide which stack to use, you'll have those libraries as available options.
You can also focus on those tools that appear in job postings, especially if your main focus is to get a job. For example, there are lots of job postings that require React. If you want to become more employable, learning that framework is a good idea.
Every now and then, it's not a bad idea to pick up a library that you find particularly interesting, even if it's just to create a toy project. That's what I recently did with Svelte, for example.
JS fatigue can be a big problem, but you can prevent it from happening.
If you liked this article, you'll love my JavaScript Newsletter.
Every other Monday, I'll send you easy and actionable steps to level up your JavaScript skills. Check it out: https://nicozerpa.com/newsletter
Top comments (5)
What I need is a date picker picker
Why am I tilting my head at this like it's a good idea
Not just Javascript fatigue but dependency hell has been killing it lately, keeping up with the latest and greatest has become a pain.
Golang, python, ruby to alleviate backend fatigue. Front end, your stuck, besides a few distant seconds.
But wasm in general and blazor in particular look like a game changer on the front end. Not for everything but high bandwidth tablet/desktop apps requiring significant compute power where payload and time to first interaction are not so important...