"Figured it was a bad idea" actually means that some people were against it because they believed semantic class names were the solution, I was one of them. This was purely ideological, it wasn't based on practical experience because everyone knew maintaining CSS was a bitch. Heck, starting a new project with the semantic CSS approach was a bitch because if you didn't spend 2 months planning ahead you'd end up with soup that was turning sour before it ever left the stove.

Bootstrap and the likes were born out of the issues the semantic approach had, and their success and numbers are a testimony to how real the issue was, and I say this as someone who never used and despised bootstrap. Maintaining semantic CSS was hard, starting was hard, the only thing that approach had going for it was this idea that you were using CSS the way it was meant to be used, it had nothing to do with the practicality. Sure, your html becomes prettier to look at, but what good is that when your clean html is just hiding the monstrosity of your CSS file? Your clean html was supposed to be beneficial to the developer experience, but it never succeeded in doing that.

[–] Aux@lemmy.world 2 points 4 months ago (1 children)

There's nothing hard about semantic naming. Especially when you're separating your elements into components and use SCSS or some other pre-processor.

[–] smooth_tea@lemmy.world 1 points 3 months ago

Either you understand that the consensus is that naming things is hard and you just want to elevate yourself above everyone else by arguing against it, or you're unaware that it is the consensus, in which case your opinion doesn't really matter because you most likely underestimate the issue.

It's such a truism that I'd suggest googling "naming things is hard*.

There are only two hard things in Computer Science: cache invalidation and naming things. -- Phil Karlton

https://www.namingthings.co/