Hacker News Reader

Comment by lloydatkinson | Hacker News Reader

Oh two tailwind hate threads today instead of the usual one at a time?

Everyone as usual saying "long class lists" even though the literal home page tells you not to do this and to make components or partial views or whatever your tool of choice calls it.

At least be inventive and follow the instructions before you start blaming something.

View on HN

If everyone using a tool is using it wrong, it’s a poorly designed tool

Everybody isn’t though, just the people who are complaining.

This is exactly it, and the person you replied to should have known this.

You simply can't look at people not reading the docs (or even the home page) who then moan about how the thing they are misusing isn't working - and then conclude it must be the fault of the thing instead of the people misusing the thing.

Some people would rather learn every CSS rule than spend 10 minutes reading the Tailwind docs.

The homepage has multiple animated examples showing the use of utility class spamming.

It's a lot of work to create components just to reduce CSS duplication (i.e. to create more components than you would make if you used traditional CSS classes.) Not always a good solution.

I do like Tailwind, for the record. It would be nice if its allies and enemies would both admit it makes tradeoffs.

It's only slightly more work than creating re-usable CSS.

I never read the docs (ok, I do, eventually) but I actually never saw that "tidbit" but it just seemed intuitive that having a million classes wasn't good... but that's why I almost always make what I need to make and then start breaking it down into components. Or, if I have a good plan, start with components. I've never had to use an absurd amount of classes.

What is the alternative?

The holiday season wouldn't be complete without the HackerNews Humbug

Reply on news.ycombinator.com