Not advice but I was once interviewed by a CTO that thought React was the bestest thing in the whole world and way better than anything else because...... it had state and props! which he stated with much glee on his face!!! while I sat there a bit puzzled!?
I had only just finished reading my React book the evening before my interview and wondered what I'd missed in the book because.... maintaining state on the web is nothing new, nor is passing properties.... Then I was told that I "didn't have enough experience" even though my experience spans into those early days of the web when we were having to figure out exactly how to maintain state on the web.
While I was in that city, the "advice" I kept getting as a LAMP developer was to learn React because "PHP was dead" (to them - mostly startups using React), then I move back to Vancouver where it is pretty clear that I should have spent my time learning Laravel instead....
I plan on picking up Laravel next calendar year because I seem to be much more employable as a LAMP developer with 20 years experience than as a React developer without any industry experience using it (and I've recently started switching to Vue because it's open source).