Rationalizing Functional CSS

This post by Marcelo Somers looks at the good and bad parts of writing functional CSS.

I loved writing really clever, powerful CSS classes. I argued for it because of “ease of developer consumption.” My goal was that a developer could add a single class to an element and it would automagically do everything for them. Basically, the opposite of functional CSS.

3 months into a functional approach to CSS architecture, I’m addicted. The times I’ve used the old monolith approach, it’s become a tedious challenge in jumping between files constantly. I think I’m convinced, but I’m still trying to rationalize scalability issues as my functional codebases grow and evolve.

I’m a massive fan of functional CSS and would highly recommend experimenting.

2 thoughts on “Rationalizing Functional CSS”

  1. What is “functional CSS”? Where’s the full article by Marcelo Somers? What is this post even about?

Comments are closed.