Vanilla CSS is the other end of the spectrum, but the problem is there is apparently nothing between hand-crafted CSS and a full front-end framework. People, like me, who are not good at design will choose the convenience of the latter over going through the tedium of the former, even if we don't really want to.
There is no design in/for the web without html+css, is there?
Edit: by removing 3rd parties from your project you remove a lot of overhead and current and future risk. But be warned: Maybe your company sells exactly that for a good margin and you ruin the business model.
> There is no design in/for the web without html+css, is there?
Only as much as there's no programming without assembly language.
It is really sad that you are forced to do things that you believe you are not capable of doing and refuse to do.
When did I ever say I was not capable of doing it? It's really sad the way you push your mindset on others.
The problem is too much reliances on frameworks and add on libraries.
Developers will import an entire framework that for the benefit of a single feature. It's mind blowing to look at the amount of js includes for seemingly simple sites.
Stackoverflow answers that direct you to import a library or framework should be banned in most cases.
I will often have to scroll past several answers that say to import a library before finding a simple and functional answer that uses only a few lines of code down near the bottom. Which in my eyes is the real answer. I often wonder if there's a behind the scenes effort on SO to promote certain includes.
The entire ecosystem of some languages / implementations relies on this far too heavily.
We are seeing some of the consequences other than just bloated systems from this style of coding with malicious node packages.