DEV Community

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

Collapse
 
essenceofchaos profile image
Frederick John

Although the author appears to be a raving lunatic, he does make at least one good point. Developers in the Novice and Advanced Beginner stages, referring to the Dreyfus model of skill acquisition, should focus on learning the foundational technologies like JavaScript and SQL instead of trying to learn a framework.

Despite being hard to read, what with the pompous tone and many, many Star Wars metaphors, the message is true enough. If you only learn a framework then you really don't know anything besides a very narrow set of specific use cases across several technologies. It doesn't behoove a novice to learn a JS framework. Instead, they should focus on mastering JavaScript, specifically es2015 and beyond. In the long run, learning how to interact with the DOM, add and remove event listeners, work within the event loop with promises or async/await, are all of greater benefit. Once you understand how the underlying technologies work then you can decide if you want to use a framework and which framework may be applicable to your use case. However, to say that, "ALL frameworks are terrible" is simply ignorant.

What is a framework anyway? Well, if you create websites or web apps you'll often find that you have a certain set of requirements that continue to come up again and again. There are certain components that can be shared across different projects, for example, a navigation bar or pagination list. Having a set of well designed pre-existing components can not only save you a lot of time but greatly improve the user experience.

Should you use a framework? Well, like the answer to many of life's questions, it depends. Each use case is different and I would caution anybody to do their due diligence before making any commitments.