Top 10 Reasons we should stop using frameworks

  1. You have more fun! Coders are fundamentally puzzle solvers. When you figure out the most elegant way to make your own inline SVGs to plot a curve or form an icon, it’s just more fun than figuring out how to make somebody else’s package do it. And why should an icon be 3k when you can do it in 100 bytes?
  2. You learn so much more that’s useful. When you write in HTML5 and Vanilla JavaScript, or you style your own navigation bar in CSS, you can learn patterns you’ll use over and over again. Someone has already solved the problem you’re working to solve, and has likely shared it somewhere.
  3. You create faster apps. An app that has to load packages will always take a bit longer than one that doesn’t.
  4. You create fixable apps. If you’ve ever had to update an app from CakePHP 2 to 3, or Bootstrap 4 to 5, you know how annoying it is when package authors change requirements that require you to change class names across a whole package of pages that depend on them. Even worse, when you have to fix an angular or react app written by someone else.
  5. The web might be OK as it is! Since I write for clarity rather than innovative artistic design, perhaps the only font I need is default sans-serif! The fact that HTML flows to fit screens is a GOOD thing — you don’t have to control every pixel.
  6. Avoid tools that manage packages. In a 2017 Medium article, Chris Pearce argues that a front-end developer should not only understand packages, they should be proficient using tools like “ Webpack, Gulp, Babel, ESLint, Stylelint, PostCSS, NPM…”. Really? Bulky tools whose only purpose it to manage the dependency hell created when you use packages?
  7. DevTools! Chrome’s built in DevTools are just plain awesome to debugging JavaScript, tinkering with CSS and debugging PWA service workers. It is particularly brilliant at teaching you how to make your app more accessible and optimized for search engines. And it is so much easier when you’re just dealing with one layer of CSS.

What would help us be free of frameworks?

8. Better Tutorials. Although I love Google, their tutorials are terrible and often out of date. A good tutorial should include the very MINIMUM you need to know to get the job done, with no styling, no extra packages to distract you — just the straight vanilla code please!

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
John Coonrod

John Coonrod

A guy committed to human dignity for all.