Why You Should Use a Web Framework 
Tags: webdev, framework, beginners, react
Published: 2018-07-26 20:16:41

---
title: Why You Should Use a Web Framework 
published: true
description: Frameworks are your friend and other opinions.
tags: webdev, framework, beginners, react
---

![](https://thepracticaldev.s3.amazonaws.com/i/obihcgs4wkecxupcnm1q.png)

Whenever I see a comment like this one: "[frameworks are making you all into bad developers](https://dev.to/gypsydave5/why-you-shouldnt-use-a-web-framework-3g24)," I figure the author just interviewed someone who couldn't answer basic questions or came out of a meeting where a junior dev suggested React for a splash page.

## What is a Framework?

I think the definition that applies to us web developers is this:

> framework: a basic structure underlying a system or concept.

A framework serves as the foundation of the website. It provides all the basic functionality that most websites need.

## Is it easier for beginners to use a framework?

Frameworks are usually very opinionated about things like code organization, programming concepts, language, structure, tooling, etc. This isn't a bad thing because you choose a framework for this reason. You want a framework that conforms to your idea of how web development should be done. 

And if you are a beginner, you have no opinions yet so the framework was probably chosen for you. As you get into it, you will find yourself saying, "oh, that's why they do that!" or "why didn't they do it this way instead?" This is good because that means you're learning!

## Is it really hard without a framework?

Building websites is not rocket science so it's *not* really that hard to do it from scratch, but frameworks exist because, aside from time and money, it's very easy to get things wrong. If you DIY it, then I guarantee you will forget something that will eventually come back to bite you in the ass.

![](https://thepracticaldev.s3.amazonaws.com/i/wznro5umovdkmtna3sl0.jpg)

I would agree if someone said don't use a new framework. Test-drive new frameworks for prototypes and such, but use stable, reliable, and tested frameworks for your real-world projects.

## Shouldn't I Learn the basics, not someone's abstraction?

The short answer is yes, please learn the basics. But... 

...good frameworks enforce and, in some cases, introduce best practices. 

...good frameworks have lots of community support. You can almost consider all the people involved in building the framework as part of your dev team.

...good frameworks are modular so you don't have to load a lot of unnecessary code just to get the bare minimum required to work your site. A lot of people mention Bootstrap when talking about why you shouldn't use a framework, but Bootstrap is fairly modular so you really don't have to load everything to make your site look great and work well. You just need to learn how to use it.

## Everyone Has an Opinion

As for the article I linked above, the one thing the author said that I agree with 1000% is this:

> Don't learn how to build React with Redux with Bootstrap with JQuery, learn HTML, CSS and JavaScript. ~ [David Wickes](https://dev.to/gypsydave5/why-you-shouldnt-use-a-web-framework-3g24)

I've interviewed a lot of front-end developers and I cringe every time one of them uses jQuery interchangeably with JavaScript. Don't do that! Especially in an interview.

![](https://thepracticaldev.s3.amazonaws.com/i/qy7pb3ywr603vcqy1c99.jpg)

When someone says "don't do this" or "do that," take that with a grain of salt. Unless it's your boss and you don't have a good counter-argument.

Learn. 

Form your own opinions. 

But, most of all, do your job in the time allotted, in the best way you know how, and always ask for help when you need it.


> The opinions expressed here are not meant to offend or otherwise hurt anyone. It's just my 2 cents.