News for hackers. Stuff that matters.
Re:Why Tailwind CSS Won by emmacharp on Wednesday August 16, 2023 @03:59PM (#37152856)
I'm not sure what you mean about "Stylelint having a problem".

There's a default config, with only base rules, without the more opinionated ones. Then you configure/extend it as you would with almost any other tool. Isn't it the way most tools of this kind work?

Or am I missing something?

Re:Why Tailwind CSS Won by marcosdumay on Friday August 18, 2023 @09:13AM (#37175157)
Linters default rules define almost completely how they will be used. It doesn't matter if you think this is reasonable or not.

IMO, missing some rules is better than what most tools of this kind do, but something as plain and obvious as "did you enable debugging symbols on the development build?" should be there. And most people will blame the tool if it's missing.

Re:Why Tailwind CSS Won by emmacharp on Friday August 18, 2023 @11:03AM (#37176656)
Sorry if I'm being obtuse but I still don't understand.

As I see it, the problem was one of SASS code architecture. What do you mean then by "enable debugging symbols"? How does that solve the "chaotic file architecture" problem?