Choosing javascript frameworks is hard. In part because I’m a seasoned dev who is past caring about shiny bells and whistles.
What I realise more and more is that I don’t care about the framework itself, how it works or any issue that it supposedly solves.
What I care about is the longevity of the framework and how useful knowing it actually is, when trying to find a job.
React wins this battle hands down and while I may fiddle with other frameworks, keeping up to date with react is still a must.
But then I’m not looking for work and if I were, I’m not sure I’d want to go in somewhere as a developer. So why even consider this?
I guess it’s my insurance. If and when something happens, it’s good to have a highly-paid, up-to-date skillset to fall back on.
Having a bunch of money saved up is nice, but nothing beats having a highly demanded, hard to find skillset.
So that’s how it goes, good web developers must always have some side project to test out new skills and frameworks against, because if we don’t, one day we might wake up obsolete.