|
|
|
|
|
|
by vogon_laureate
709 days ago
|
|
|
This gives big bikeshedding vibes. I always liked the idea of semantic markup, but humans are messy and complex and we will always find ways to bring that chaos to utopian systems. Classes and IDs work fine most of the time. Documenting your styles is good practice. Using BEM or Tailwind has the benefit of adhering to a system and base classes that others can make sense of without much effort. CSS is OK. Our energies are better spent on more important things. |
|
|
The rise of React and SSG/SSR means there is a world where the classes are React components and the attributes are props.
Even for static pages, for DX you can use the same tooling as you are used to for dynamic pages. And something like NextJS can generate the static html.
And this makes even more sense for dynamic stuff like date pickers.
In this world you use utility classes because tags are too granular and components are the logical unit.
But if you are hand crafting the html then tailwind might be more of a pain. I am a bit undecided on that. I still have a soft spot for CSS Zen Garden.