2022-05-18
1760
#css
Nelson Michael
106484
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:

Wasm 3 Before GTA 6 LogRocket Article

We got Wasm 3.0 before GTA 6: Meet the web’s new engine

Discover how WebAssembly 3.0’s garbage collector, exception handling, and Memory64 transform Wasm into a true mainstream web platform.

Ikeh Akinyemi
Oct 3, 2025 ⋅ 2 min read

How to use AI to build accurate ShadCN components

AI agents often break shadcn/ui components with outdated docs or made-up props. The MCP server fixes this by giving live access to registries. In this tutorial, we’ll set it up and build a Kanban board to show it in action.

Chizaram Ken
Oct 3, 2025 ⋅ 5 min read
Rust Project for Web Services LogRocket Article

The best way to structure Rust web services

Learn how to structure Rust web services with clean architecture, Cargo workspaces, and modular crates for scalable, maintainable backends.

Jude Miracle
Oct 2, 2025 ⋅ 2 min read
andrew evans headshot

A spec-first workflow for building with agentic AI

Andrew Evans gives his take on agentic AI and walks through a step-by-step method to build a spec-first workflow using Claude Code.

Andrew Evans
Oct 1, 2025 ⋅ 18 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