You learn js, then you learn a bit about ts and pick react/vue if you want to do frontend or nodejs if you're into backend. Then you do something basic, like a barebones twitter clone, weather app, etc. By the point when you're 80% done, you will know most important parts of the ecosystem naturally

After that, learning all the supporting libraries/frameworks is super simple since next is just superset around react, same for nuxt. Solid, svelte, fresh etc are just different flavors of react. Even vue is looking like react this days with composition api, simply because they nailed the simplicity and dev comfort. Average dev will never face weird js/ts parts or confusing libraries because most of their day to day job will be moving buttons and looking how to persist user basket in browser storage...

Sure there are a lot of libraries and ways to do stuff, but 90% of them are irrelevant, only-for-hobby or simply dead and unused since 2010. Knowing ts+(react|vue)+(vuex|redux-tk|mobx)+(styled|tailwind) will land someone a basic job where they can progress and expand their knowledge lol

[–] faintbeep@lemm.ee 3 points 1 year ago

What happened was, up until the early 2010s a lot of frontend developers were essentially designers who could write HTML/CSS templates, but not programs. When the industry shifted to client side SPAs they couldn't follow, so there was a big backlash against the new "complicated" tooling, even though it's no more complicated than any other domain.

I always wanted to write a response post, "How it feels to learn JavaScript in 1996". Because yes, webpack is harder than flat JS files. But you have 1 billion tutorial videos to help you do it, and open source project skeletons to start you off, and Q&A sites to fix your problems for you.

Some of us learned JS before YouTube or StackOverflow or even W3Schools existed. When I got my first job browsers didn't even have developer tools! If your code didn't work you just had to guess why!

load more comments (7 replies)