@Gargron Can confirm that it is really useful. Speeds up development a lot. I tried a lot of CSS concepts over the years and found out atomic and utility first is what I like best and what is also maintainable as its a read what you get approach to UI development. No digging and debugging of bloated, legacy CSS code, no inheritance shizzle, no questions when reading HTML. Small fixes and improvements can be done directly in the template without the cognitive load of CSS files next to it.
@Gargron If you’re not good at CSS, it can help you achieve simple things. Or if you want to quickly prototype an idea, maybe it can help you, too.
Using a utility-first framework like this comes at the price:
- useless entry gate for CSS (tooling + backwards mental model);
- bloated HTML payloads for your user (because HTML often doesn’t cache really) and less maintainable HTML because it’ll be hard-the-fuck to read until you’ve extracted it into components.
The original server operated by the Mastodon gGmbH non-profit