Post

tobias
@moeritz.io

still 50/50 thorn between "tailwind 4 is the perfect evolution" and "i wish they just added oxide to tailwind 3 and called it a day"

tobias
@moeritz.io

I dislike that everything is available as CSS variable by default. I don't want any perspective related variables in my project if I don't use the perspective utility class once. If Tailwind can scan for 'text-green-500', surely it should be possible to scan for 'var(--color-green-500)'?

tobias
@moeritz.io

One thing still missing is being able to set the breakpoints as 'max-width' instead of 'min-width' (in theme.css, works with legacy js config). I want that 'md:' targets all devices below the size, not above. I know you can use 'max-md:' - but I don't want to shift my mental memory after 3 years.

0 reposts1 like

tobias
@moeritz.io

In general, the CSS config format feels more bloaty, less elegant to me - especially the font declaration. For example, I now have to add line-height, letter-spacing & font-weight separately to each font size instead of being able to pass one global object.

tobias
@moeritz.io

I was very much happy with Tailwind in the beginning, because *it was opiniated*. I disliked UnoCSS because with the default preset, you could mix Tailwind, Bootstrap and Tachyons styles in the same project. The configuration effort was much larger. Either have I matured and got to know better what

tobias
@moeritz.io

I want or Tailwind just shifted too far away from the origin. This sounds a bit harsh, I still love Tailwind and their wonderful influence on making CSS a bit easier for everyone ❤️