Utility CSS vs. BEM. Not the problem you thought..
https://frontstuff.io/in-defense-of...

What a piece of crap. I mean look at this gem right from the article:
<h2 class="font-16 font-bold font-purple">

That's so moronic that the author's opinion on HTML/CSS doesn't count more than a fart of neighbour's dog. Great example of folks who are still deeply into the bad old days of HTML 3.

@Fast-Nop

I know! Horrible, just terrible! The humanity!

Imagine trying to keep your site with a standard look and feel and needing to copy and paste 30 CSS micro classes for each h1 tag. Disgusting.

@AlgoRythm And then you introduce several or just a different skin and either get misleading class names or have to touch the markup again. But nooooo, HTML 3 was soooo cool that assholes needs to replicate it with whatever means they have.

I touched a nerve.

This is definitely gonna be my goto issue whenever I want to mess with web developers.

Made an account just to say I read your whole article and couldn't agree more.

BEM is to CSS what OOP is to JS.

And I'm already sick of it. Programmers need to learn that CSS is iteration and reiteration. You're never going to make X amount of classes in some inane naming convention, apply them to your templating system, and then never have to write CSS ever again. It's never going to happen. And I hate that I'm expected to think that way.

Utility first all the way, baybeeee. It's flexible, readable, and extremely easy to pick up. Onboarding any BEM codebase is a chore and a slogfest, and you always run into "oh, we haven't made a component for that yet". Why make a whole component when you can just tweak existing ones for edge cases? Why even make whole components for edge cases at all?

So hear hear, author. Keep preaching the gospel. Let Tailwind set us all free. Amen.