The struggle is real! As a former full stack dev who transitioned into frontend only (and still have trouble keeping up), my suggestion on the frontend side is

The struggle is real! As a former full stack dev who transitioned into frontend only (and still have trouble keeping up), my suggestion on the frontend side is also (like everyone else is saying) to not chase everything. Just pick one of two (probably Next, because it's the most popular and heaviest) and just learn that well. The other frameworks are much simpler and can be picked up as necessary if an employer needs it. Many of them use JSX as well and copy the rest of Next's tool chain config (bundler, tester, Typescript, linter, etc.) So basically by learning Next and vanilla JS well, none of the rest should be too hard. If you really have extra time, you can always build side projects (or even just the same prototype) in different frameworks to learn and compare. But honestly a lot of them will just die out before they see any substantial real world usage. i wouldn't bother with most of them. They're just fashion trends. I think React and Next are the only sure bets in the JS/web frontend world right now. Learning the rest are bonuses. If I had a lot of extra time, I'd probably learn Vue/Nuxt, SvelteKit, and HTMX/Alpine. ----- What about on the backend? Back in my day it was mostly just Java, Rails, PHP, microservices, etc. These days there are so many container management systems (k8s? docker? some Google thing?). And entire new languages like Rust and Elixir. Not sure what to chase there either. Is there a movement towards a heavy batteries included framework (like Next on the frontend)? Something like what Rails or Laravel/Symfony provided?