I’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 t…
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.
Just sharing that the root cause is most developers don’t want to pick up an additional syntax when they already have the fundamentals
The main problem is the premise of tailwind
Every single web design on earth is a compound opinion on like a few hundred popular properties and values
They put all that in one style sheet
Which became the one style sheet on earth
Which made it possible to summon all those styles directly from within our apps
Tailwind is like the chess of utilities. There’s only so many opening and closing moves that running a business on it is incredibly difficult, given supply and demand.