DEV Community

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

Collapse
 
juni profile image
Junaid Anwar • Edited

Using frameworks/library is not as bad as this article describes it. I remember when I first started to learn Javascript, I never understood why they use document.selectElementById or selectElementByClassName or QuerySelectorAll or QuerySelector instead of just using $(".element"). jQuery made it easier for me to reason about why I loved Javascript. I was able to deliver something very quickly (that gave my client confidence to rely on me, plus made me feel more comfortable with javascript). If you start developing in a core language at first, you'll suffocate because of the complexity it hold for you as an inexperienced developer).

You willbecome a better developer if you dig deeper into the concept of a framework.

React now a days is doing a very good job in teaching you the core concepts of Javascript.

You will become a good developer when you start learning about the frameworks.

The better advice I would give to a newbie is:

Deliver your job with a framework/library but don't stop learning the core concepts of the language itself. Explore the things how they work under the hood. Read code of these libraries and frameworks. There are gems to explore in these libraries/frameworks.