I was in a similar position and the book Rediscovering JavaScript helped me understand syntax and structural changes, which made learning about new frameworks and tools easier.
Had a quick look at it. It skims/oversimplifies some important aspects that are famous in JS community to cause all sorts of issues down the line. Maybe you don't know JS would be better?
Ask HN: Where to start with getting back into front end?
11–15 of 15 posts
Re: Ask HN: Where to start with getting back into front end?
#12The basics are the same as they've been for a long time. You can easily build a working front end app using html/css/js in a single file. Build a few projects so you can familiarize yourself with modern apis without the burden of tooling. Once you've built a few small projects, hopefully you'll have a sense of the pain points modern frameworks fix. Most people use global variables for state or even store their state…
Re: Ask HN: Where to start with getting back into front end?
#13The basics are the same as they've been for a long time. You can easily build a working front end app using html/css/js in a single file. Build a few projects so you can familiarize yourself with modern apis without the burden of tooling. Once you've built a few small projects, hopefully you'll have a sense of the pain points modern frameworks fix. Most people use global variables for state or even store their state…
Our team uses hooks only, as we found classes distasteful. Most projects can be built without redux, too. React + tailwind goes a long way, lol, but yea redux has its own use case if and only if you need it
I'm sure redux has a few use cases, but the primary use case I've seen is "I've coded myself into a corner and I don't want to refactor anything."
Re: Ask HN: Where to start with getting back into front end?
#14Re: Ask HN: Where to start with getting back into front end?
#15Also this is just my own observation, your mileage may vary, but when back end teams are tasked with upgrading front end tech they pick Angular, and when experienced front end guys are given a project for a tech refresh/rewrite they go with React.
Most build tool arguments IMHO are weeds. Core is having a goal - something you need to get working on a deadline. That tends to be a great weedkiller.