logoalt Hacker News

grsmvgtoday at 8:29 AM4 repliesview on HN

As a 26+ year frontender, years ago I was against it on so many levels. Until I tried it.

Never looked back. Also, inheriting projects with someone else’s code is fine. Just a quick look at the central config and you’re good to go.


Replies

arnejenssentoday at 8:42 AM

Tailwind looks bad on "paper". It violates a lot of "best practices". It is ugly. Yet in reality it works. It gets the job done. It is fast to work with.

Constraints are known to enhance creativity.

show 3 replies
jonwinstanleytoday at 10:06 AM

Totally agree. It does break the rules, but it feels so much faster than defining class names.

On simple projects I usually @apply tailwind styles to standard elements like headings, block quote, aside, nav etc. Then just use semantic html.

Looks good and takes so little effort.

mexicocitinlueztoday at 12:28 PM

I felt the same way with JSX. Started using it and don't want to look back. Same with Tailwind.

ejoebstltoday at 8:46 AM

100% this. It looks terrible until you try it and it starts making so much sense.

Also works great with agent assisted development.