zlacker

[parent] [thread] 4 comments
1. martin+(OP)[view] [source] 2025-05-06 18:30:04
Bwoah it's almost as if react and tailwind is the bees knees ind frontend atm
replies(1): >>byeart+dj
2. byeart+dj[view] [source] 2025-05-06 20:36:55
>>martin+(OP)
Sadly. Tailwind is so oof in my opinion. Lets import megabytes just so we don't have to write 5 whole CSS classes. I mean just copy paste the code.

Don't get me stared on how ugly the HTML becomes when most tags have 20 f*cking classes which could have been two.

replies(2): >>johnfn+wm >>martin+z61
◧◩
3. johnfn+wm[view] [source] [discussion] 2025-05-06 21:01:13
>>byeart+dj
In most reasonably-sized websites, Tailwind will decrease overall bundle size when compared to other ways of writing CSS. Which is less code, 100 instances of "margin-left: 8px" or 100 instances of "ml-2" (and a single definition for ml-2)? Tailwind will dead-code eliminate all rules you're not using.

In typical production environments tailwind is only around 10kb[1].

[1]: https://v3.tailwindcss.com/docs/optimizing-for-production

replies(1): >>andyba+VW
◧◩◪
4. andyba+VW[view] [source] [discussion] 2025-05-07 03:00:57
>>johnfn+wm
So. We've moved rom "human compiler" to "human compression encoder"?
◧◩
5. martin+z61[view] [source] [discussion] 2025-05-07 05:07:05
>>byeart+dj
You're doing it wrong. Tailwind is endlessly customizable and after compilation is only kilobytes. But yes lets complain because we don't understand the tooling....
[go to top]