News for hackers. Stuff that matters.
Re:Why Tailwind CSS Won by Greed on Wednesday August 16, 2023 @06:04AM (#37144896)
It's too bad that SASS has fallen out of favor. With SASS, that would have been:

```

  a.link
    border: red

    &:hover
      border: blue
```
Re:Why Tailwind CSS Won by mcny on Wednesday August 16, 2023 @06:14AM (#37144952)
CSS nesting will be available to us mortals (in production) within a year and we might be able to use it just a guess as early as 2026?

https://webkit.org/blog/13813/try-css-nesting-today-in-safar...

Re:Why Tailwind CSS Won by fortyseven on Wednesday August 16, 2023 @06:10AM (#37144933)
Fallen out of favor with who?
Re:Why Tailwind CSS Won by blitz_skull on Wednesday August 16, 2023 @08:20AM (#37145922)
That misses the point. This is still worse than seeing all your styles in the place where they apply. SASS/LESS just make it faster and more succinct to write styles in css files rather than in the components in which they live and even more importantly—on the actual ELEMENTS that they apply to.
Re:Why Tailwind CSS Won by blowski on Wednesday August 16, 2023 @10:05AM (#37147202)
Yes, I did use SASS before Tailwind (and Compass back in the day), and got a lot of value from them. Where it started to get painful is when I have:

    a.link {
    
    }

    a.another {

    }

    <a class="another link">...</a>
It was easy to fix, but hard to scale the fixes over different codebases, timelines, and developers. That's the problem Tailwind solves for me.