Vanilla JS - not enough new devs know enough about the base API and interface that Javascript has with a browser.
Moreover, new developers are very happy to include a mass of frameworks, extensions and build pipelines to their code without having much of an idea of what they do or how they affect the work they produce.
Learning a single framework to be "your framework" can be super dangerous. What if that framework falls out of favour? I mean, learning is always part of the job, but imagine having to switch from React to Vue while trying to support a live product. That's the stuff of nightmares.
If new developers start their knowledge at the bottom level, rather than through the lens of an opinionated framework then picking up framework x no longer becomes a problem.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Vanilla JS - not enough new devs know enough about the base API and interface that Javascript has with a browser.
Moreover, new developers are very happy to include a mass of frameworks, extensions and build pipelines to their code without having much of an idea of what they do or how they affect the work they produce.
Learning a single framework to be "your framework" can be super dangerous. What if that framework falls out of favour? I mean, learning is always part of the job, but imagine having to switch from React to Vue while trying to support a live product. That's the stuff of nightmares.
If new developers start their knowledge at the bottom level, rather than through the lens of an opinionated framework then picking up framework x no longer becomes a problem.