alt Hacker NewsI’ll be honest.
I’m a contributor to this.
I’ve been CSS since the mid 2000s and I have a lot of it memorized by heart.
My team uses tailwind, therefore I use tailwind
But I don’t want to reconfigure my mental model to think in esoteric shorthand, when I already have vanilla web tech memorized.
So I just write some code to match the design and then I let an llm transform it into what my team expects.
I’m sharing in the hopes that the tailwind team can figure out a middle ground because I think a service that can take any valid styled content and output the same result in tailwind would be a niche small language model that solves the use case for why I don’t go to the docs.
Replies
Every project I worked on that used CSS was a mess. It's always 1000 line SCSS files and nobody knows what is going on there.
The shorthand makes inline style more ergonomic, so you can see the wood for the trees, rather than long strings of style attributes in your markup.
Inline style is the thing. That's what tailwind is enabling in a readable way. And inlined style is what makes style more maintainable and less susceptible to override rot.
The separation between form and function is always a bit illusionary, but particularly so with CSS. Almost all markup is written to look a specific way, not a configurable way.