Hacker News Reader

Comment by omgitsabird | Hacker News Reader

> CSS is effectively solved. Tailwind CSS is the best thing to ever happen to CSS. I cannot imagine ever writing CSS in a separate file and having to think of names for elements. It's also an excellent resource for beginners.

I work with developers still have difficulty with concepts like specificity and cascading even though they have been working with CSS for many years.

I don't think statements like this are true or encouraging.

View on HN

Tailwind kind of makes specificity and the cascade a non issue, though. Sounds like it might be just the thing for these developers.

Yes, and I would argue that many people using frameworks like these never learn those fundamental concepts.

I'd argue that never learning is the primary reason those frameworks exist.

Plenty of web devs understand how specificity and the cascade work. That doesn't meant that they work well. CSS is full of examples of good-sounding ideas that didn't pan out.

Frankly the whole thing works better when you avoid touching the cascade as much as possible. Which is why these atomic frameworks are modeled this way.

I thought that was a weird statement. Tailwind solves (kind of, to me) the problem of organizing CSS. I mean, you still have to pick the right rules to write.

Isn't Tailwind the one where you write inline styles with classnames instead of inline styles? How's that good?

Yes, there is nothing good or bad in it nor it's something new - we already experienced it in the form of `Atomic CSS` and other similar - it's just another swing of the pendulum, for some use cases it's good and will bring joy and fast development pace, for some use cases it's not good and will bring pain after honeymoon is over.

It seems like a reimagining of the style HTML attribute to me.

Reply on news.ycombinator.com