In simple words this post is about, From the excitement of learning a syntax to diving deeper into the internals of frameworks and to make the right decision for each application.
Yes, there are jobs out there that pay if one knows how to use a framework. They are good to start with. But in parallel, if the effort is not put in learning the basics of the language, the engine that runs and the interactivity - it may get hard to build a career by switching to learn the usage of frameworks.
If we take two-way binding or virtual-dom, we should put the effort into learning why they are needed and when. If we get to read, "use redux only when needed", it's good to take the next step in knowing why is it said so.
If we don't do this, frameworks over frameworks will keep the developers rolling from one knowledge base to another.
When enough developers do this, the companies can form a team of core-language developers and not use any frameworks in a lot many scenarios. Many companies take a decision to use a framework because it gives them stability due to the availability of framework-developers.
In the long run, if we create framework developers, it would be an inefficient usage of
developer base' learning-time as someone who might have put 4-5 years in a framework might see another framework gaining more attention.
This is not against any frameworks, they are needed because we lack in teams that can build the same with the base knowledge of a language alone. In the past, companies have seen instability with the same. Also, they are very much needed in a few scenarios where the requirements match the need.
It was to remind us(especially myself) to learn any core language in depth.
I am a frontend developer. This may not apply for a few backend scenarios which I might not be aware of. Thanks for reading!