Because how dare there be MULTIPLE reasons not to use them, legitimate reasons at that? That's not "veering across the board" -- you make it sound like a moving goalpost. ALL of those reasons are valid concerns, and are why it's mind-numbingly dumbass that anyone would use this garbage by choice!

And I'll give you another reason too... These CSS frameworks dragging HTML practices back to the WORST of mid-1990's browser wars derpitude! But sure, I'm the one stuck in the past... not the people recreating everything that was wrong with HTML 3.2 by pissing presentational classes all over their markup.

Pure comedy how these "frameworks" drag practices back 25 years, but we always get people saying "oh you just don't like anything new". What a crock!

I love new technologies when they're IMPROVEMENTS, like the constant improvements to ECMAScript resulting in less "making functions to do things that should have been in the language twenty years ago" (see actual classes), or how CSS keeps maturing to the point that around two thirds of what people still do with JS doesn't warrant scripting any more... or in some cases NEVER needed JS in the first place. (mobile/hamburger menus much?)

Any alleged improvements brought by the majority of these frameworks are unfounded nonsensical propaganda based in no way, shape, or form in reality. It's outright delusional!

And you want to talk "real business problems?" You mean like choking out servers connection limits, increased hosting and maintenance costs, wasting time turning weeks into months, not having anyone end up qualified to actually fix things because all they know how to do is copy / paste and run to Stack Overflow when things go wrong? Much less getting dragged into court over accessibility issues?

I work as an accessibility and efficiency consultant, and those are the issues I'm constantly and consistently fixing for clients, and the vast majority of the time these bloated, broken, inaccessible, halfwitted frameworks are the leading cause of those problems!

Though you're right on one thing, it's POSSIBLE to make bloated wrecks in vanilla HTML/CSS, but the problem is I've yet to see a framework where it's possible to make a clean page. Much akin to what Asimov said about science. It's not so much that scientists are always correct, but that non-scientists are usually incorrect.

MAYBE if people stopped wasting 100k of HTML to do 20k's job, 500k of CSS in a half dozen files to do 48k's job, and two megabytes of scriptttardery in dozens of files on sites where 64k of JS would be overkill IF IT EVEN NEEDS SCRIPTING IN THE FIRST PLACE, they wouldn't be so easily suckered by dipshit garbage like front-end frameworks... or SPA in cases where it's just not worth the time and effort, and/or provides no benefits fixing the bloody markup would.

'Cause far too often things like SPA are nothing more than band-aids on .50 cal bullet holes. Throwing good code after bad.