25 developers working in the same module? Without a common style?
Afaik we came from plain CSS -> BEM, because scoping styles was hard, so people found a discipline in naming things to isolate styling. Scoping did not exist in CSS.
Then we got a movement from BEM -> Tailwind, because doing the scoping by hand was a bit difficult(?)
Then we get Tailwind -> Tailwind + DaisyUI because Tailwind results in messy concretion.
--------
The question I have: are the modularity/scoping primitives in modern css good enough now, rendering Tailwind e.a obsolete?
Are we still using Tailwind because people do not understand the original problem?
Going from plain CSS to BEM more or less meant abandoning the "cascade" part of CSS. We've basically spent the last 15 years styling our markup directly, bouncing back and forth between different strategies for doing so in the most capable, and aesthetically palatable way possible.
Afaik we came from plain CSS -> BEM, because scoping styles was hard, so people found a discipline in naming things to isolate styling. Scoping did not exist in CSS.
Then we got a movement from BEM -> Tailwind, because doing the scoping by hand was a bit difficult(?)
Then we get Tailwind -> Tailwind + DaisyUI because Tailwind results in messy concretion.
--------
The question I have: are the modularity/scoping primitives in modern css good enough now, rendering Tailwind e.a obsolete?
Are we still using Tailwind because people do not understand the original problem?
Maybe someone can enlighten me.