Jason Knight
2 min readNov 17, 2022

This is a poster child for what I mean when I talk about "SPA for nothing" alongside how the users of React and Failwind don't know enough HTML or CSS to be making websites.

It's bad enough the lack of content for scripting off/blocked users because of React's idiocy being shoe-horned in where it has no business, without the presentational classes and general lack of proper semantics so typical of those screaming "wah wah, eye dunz wunna lurn teh CSS" allowing themselves to get suckered by failwind.

No valid H1 candidate, H1 doing H2's job, SPAN doing H3's job, endless pointless DIV and SPAN for nothing, presentational classes slopped all over the blasted thing... 100% typical of the "screen users only, screw speech, braille, and search" attitude.

Hardly a shock it ends up 152k of JavaScript nonsense on a page that shouldn't even have client-side scripting, to deliver 402 bytes of plaintext with zero content media. (the images present all being presentational)... aka not even 3k of HTML and 10k of CSS' flipping job!

But sure, tell me again how much "easier" this way of dealing with sites and their content is.

EVERYTHING you've been told about these systems is a lie. I'm going to make my own article with a rewrite of this to illustrate what I mean. The people who CREATED React and Failwind don't know enough about HTML or CSS to make websites, much less tell the rest of us how to do so. You've been saddled up, hoodwinked, and taken for a ride by their wild unfounded claims and outright lies over how much "easier" their way of doing things is.

Jason Knight

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