How sad that this has become the widely accepted narrative.
There’s a lot of value right now in NOT building things that way.
Last week I had to deal with fixing another dev’s mess on a stuck project.
Big company website, but nothing fancy at all. Purely a marketing window. The amount of complexity he put into it by using Vue.js was insane for the scope of the project. INSANE.
To do something as easy as changing the pages <title> tag we had to write an unjustified amount of lines of code.
Framework-itis really is a bad disease, it not only affects your work, but it definitely clouds the simplest form of judgement, it appears.
Then we have exactly this: someone who got a hammer and spent years treating everything like a nail comes to a reckoning, usually framed as a longing for the good old days when things used to be simple.
Well, you know, things can still be simple, if you don’t offload to unjustifiably complex frameworks the duty of understanding what’s going on in your project.
To be clear, I’m not at all against frameworks. I love and use some of them, but they’re like a closet. If you are a tidy and organized person, your closet will be full of neatly folded clothes; if you’re a messy person, it will still be a repository for heaps of displaced garments, ready to fall out as soon as you open the door.
He might just be that kind of JS dev that really likes to build a webpack castle.
You know, if you can drop in a url to a cdn-distributed version of a JS, you'll instead rebuild the whole thing in webpack, babel, and several other things just to be able to type "import".
(I don't know Vue, but this smells a bit.)
We wanted an internal component to be able to change the page title, which ended up with a project to transition to using react-helmet. It ended up taking a few weeks before this project completed.
const setTitle = (t: string): void => document.title = t
We also couldn't console.log in this codebase, it was very ideologically pure but it took ages to make any changes
However, I've also seen simple pages that are line by line copies of tutorials for whole sites, pared down to a single page.
Frameworks aren't bad, unstructured working practices and environments often breed this sort of toxicity in code.