this post was submitted on 20 Aug 2023
-3 points (33.3% liked)

Web Development

0 readers
1 users here now

Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 1 year ago
MODERATORS
 

cross-posted from: https://programming.dev/post/1923251

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
[–] g6d3np81@kbin.social 2 points 1 year ago* (last edited 1 year ago) (1 children)

BEM is are methodology about atomic code design, it gives you a standards and guides how to simplify code maintaining.

Isn't this also what Tailwind, UNOCSS and the likes about?
Sounds like he have a problem where working in project using BEM, different team use it in different way (which I think as what to expect). And when components are involved, is CSS convention really the focus here?

edit: ok, I think I finally got your point...
How does BEM differ from OOCSS, AMCSS, SMACSS, SUITCSS?
Well... this thing feels like frontend framework with extra step.

[–] vitonsky@programming.dev 1 points 1 year ago (1 children)

If you think a Object Oriented Programming is a framework, then you can think about BEM like a framework too. But a correct word is a methodology. A "framework" have too generic meaning.

Methodology gives us a methods how to improve software quality. This methods like an interfaces in programming that we must implement as programmers

[–] g6d3np81@kbin.social 1 points 1 year ago

I see. I might have done things in similar way without realizing what it is by just focusing on decoupling and reusability.