Nelson Michael
May 18, 2022 ⋅ 6 min read

BEM vs. SMACSS: Comparing CSS methodologies

Nelson Michael Nelson Michael is a frontend developer from Nigeria. When he's not meddling with CSS, he spends his time writing, sharing what he knows, and playing games.

Recent posts:

Developing Web Extensions With Wxt

Developing web extensions with the WXT library

Browser extensions are an important part of the web ecosystem. They make our lives easier and enhance our web browsing […]

Debjyoti Banerjee
May 24, 2024 ⋅ 8 min read
Bulma Css Adoption Guide: Overview, Examples, And Alternatives

Bulma CSS adoption guide: Overview, examples, and alternatives

Explore how Bulma CSS simplifies frontend development with its ease of use and customizable, responsive, pre-designed UI elements.

Timonwa Akintokun
May 23, 2024 ⋅ 10 min read
Using Mountaineer To Develop A React App With Python

Using Mountaineer to develop a React app with Python

Develop a React app with Python using the Mountaineer framework for building a simple app with integrated your frontend and backend database.

Rosario De Chiara
May 23, 2024 ⋅ 7 min read
Enhance CSS View Transitions With Velevette

Enhance CSS view transitions with Velvette

Velvette is a utility library developed to make working with view transitions easier.

David Omotayo
May 22, 2024 ⋅ 9 min read
View all posts

3 Replies to "BEM vs. SMACSS: Comparing CSS methodologies"

  1. I’m really against any naming methodologies. Modern CSS-in-JS solutions simply remove this overhead. The best conventions are the ones that are not needed!

  2. “and you can change the appearance and behavior of components to fit the context they’re placed in using modifiers.”

    This is plain wrong because BEM does not allow cascading. So one would need to add the modifier to every element. This results in an extreme overhead of both HTML class attributes and matching css selectors.

Leave a Reply