Jason Knight
3 min readOct 27, 2022

--

-You really forgot the biggest cons for Failwind and Webblows. The pissing on caching models, screen media only mentality, and general reek of ignorance on the part of their CREATORS on the most basic use of HTML and CSS. Particularly in failwind's case where every official example, as well as the very nature by which it works telling users with accessibility needs to go f*** themselves.

And they're not "utility classes". That's marketing propaganda "bullshit bingo" meant to distract from the fact that what's actually being done is PRESENTATIONAL CLASSES. And if you know the first damned thing about HTML you know that presentation -- saying what things look like -- has ZERO business in your markup! NONE! Why?

Because HTML is about more than what things look like for screen users. Aural/speech, braille, search... All different types of UA's that don't give a flying purple fish about your visual layout and style, Or print, where you might have different style entirely. Or light/dark where the colours you declare are different for the target... and pissing in even MORE classes to say what your dark mode colours are is just going full Gungan.

Jar Jar: and meesa sayz yew nevah goes FULL Gungan.

The inept GARBAGE vomited up by the people who created idiocy like Failwind and Bootcrap is only met in equal measure by the absolute chazerei created with them.

A situation only exacerbated by the bald faced lies and propaganda driven bunk snake oil peddling claims. It is not "easier" or "better for collaboration" in any way, shape or form becuase quite literally ALL it does is create classes for every CSS property and then use them to take a steaming dump on the markup! That's it, that's ll that "utility" BULLSHIT is!

Lies don't make it fact, no matter how many ignorant fools blindly believe the marketing speil.

And malarkey like webflow only makes it worse suckering people who don't know any better with a "visuals first" approach that results in broken websites GUARANTEED to get you sued for accessibility violations if used for any serious company or site! Look at the use of pixel metrics, lack of scripting off graceful degradation, scripttardery on pages that don't even warrant the presence of JavaScript, the use of tags and attributes that haven't been valid in 25 freaking years! Anyone who thinks what that dung-heap makes is worth a damn probably needs their head examined.

Both are exactly the type of garbage I've spent the past 12 years mopping up after lawsuit after lawsuit, failing business after failing business. And thanks to apologism like your article, bandwagon cult-like worship, blind belief in whatever's "popular", and endless mindless bullshit propaganda, I've had to fight my customers staff, developers, and even the customers themselves because they refuse to believe all that BS is why they're in trouble!

ENOUGH! It's bullshit made by bullshitters, that suckers nubes and rubes alike with glittering generalities, disinformation, card stacking, and simply taking advantage of the mental failings common to most marks.

But let me tell you what I really think. You want to stop having debate about it? Admit that these garbage "frameworks", "libraries", and "no code" systems are nothing more than predatory dirtbag scams made by people unqualified to flap their yap about websites or web technologies!

https://medium.com/codex/stop-fighting-the-reason-css-exists-with-these-dumbass-frameworks-91732f5993c7

--

--

Jason Knight
Jason Knight

Written by Jason Knight

Accessibility and Efficiency Consultant, Web Developer, Musician, and just general pain in the arse

Responses (1)