“Semantic UI” Doesn’t Even Use Semantic Markup!

Jason Knight
CodeX
Published in
10 min readDec 20, 2021

--

Utter and Total. You want a poster child for why frameworks suck, this one is my new go-to to show how broken and dumbass the very concept is.

Warning, this article is not going to “play nice” or use soothing-syrup words to slap the rose coloured glasses on your head. This inane trash is 100% scumbag bullshit. You can’t handle a few harsh words mated to the truth, please, just get the F*** out of my article NOW! You want to continue spreading the LIES then you aren’t welcome.

My distaste for the mentally enfeebled ignorant trash that are front-end frameworks is by this point painfully well documented. Every time I dive into another one it’s an even bigger mess that what came before it.

This time around we have the absurdly named “Semantic UI” which to be brutally frank in every example and means by which it works flips the bird at semantic markup. It’s bad enough slopping presentational classes onto things dragging practices back to the worst of late ‘90’s pre-css practices.

No, these clowns double down by throwing the word “semantic” in the name when it is NOTHING OF THE SORT!

Semantic markup — in HTML’s case — is using TAGS to say what things ARE or WOULD BE in a professionally written document based on grammatical and structural norms. This is because the target audience for semantic markup is not developers or for programs to talk to each-other, it’s to instruct the user-agent (a browser is a ua but a ua isn’t always a…

--

--

Jason Knight
CodeX

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