DEV Community

Discussion on: Why You Shouldn't Use A Web Framework

Collapse
 
pr3tori4n profile image
Harry Robbins

I agree with the basic premise - that people jump to frameworks to accelerate their productivity as a crutch, rather than taking the time to learn the basics. And I believe its effective - hence the popularity. But it's a double-edged sword. If that framework goes out of fashion - many of the things you knew how to do evaporate with that frameworks popularity.

So yea, don't ankle bracelet your effectiveness as a web developer to any one tool or library.

BUT, there is one big problem with this viewpoint. The job market. What do you tell a web developer trying to find work who is only seeing postings for "React Developer" or "Angular Specialist". I think the economy and start-up execs are making these decisions, not the average joe developer. So what does the average joe developer do in a world where they need to get a job, but > 50% of companies want experience with a framework? I think most people simply accept, "if you can't beat em, join em." We all need to eat. What do you recommend?