Programming

17035 readers

515 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

BEM methodology is not about CSS (vitonsky.net)

submitted 1 year ago by vitonsky@programming.dev to c/programming@programming.dev

6 comments fedilink hide all child comments

Some frontend developers know the BEM methodology as a naming convention for CSS and they create a disgusting #webcomponents. I've explain the essence of BEM and shown the benefits for your frontend projects.

Feel free to share it with a people who tells you "i use CSS-modules, so i no needs a BEM"

you are viewing a single comment's thread
view the rest of the comments

[–] marcos@lemmy.world 4 points 1 year ago

I do agree.

Given that naming the element only and selecting for the hierarchy gives you completely equivalent functionality, with completely equivalent selectors, I do prefer the option that keeps the names more generic.

BEM always looked like a hack to increase the CSS selection performance, and not something that adds architectural value. And well, we don't need hacks of that level anymore, browsers are well optimized nowadays.