Sorry but it's bad enough wuck-fittery like bootcrap and failwind sharting presentation into the markup pissing on caching models, HTTP parallelism, media targets, and indeed the very reason CSS even exists in the first place... without then going 100% Pakled clumpship Pakled by putting behavior in the markup too resulting in even bigger inefficiencies and further saying "accessibility? Who gives a shit"

Same herp, just a different derp. Considering how many back-end programmers lose their freaking minds if a function is more than six lines long, or insist on using a separate file for every 12 lines of code through "modules" because they're too dumb to handle naming things, or outright lose their shit if they see a monolithic stylesheet or scripting file? Well, it's hard to grasp why y'all have such a hardon for shoving EVERYTHING into the markup recreating the exact same problems.

Made all the harder to understand by the fact the more you crap into the markup, the more code you have to write as part of the back-end that could / should be handled separately by the front-end developer or at least in a thousand times simpler a manner.

We need a new catchphrase. "That markup does too much"