News for hackers. Stuff that matters.
Re:Tailwind vs. Semantic CSS by flagrant_taco on Monday October 23, 2023 @09:24AM (#37985243)
There are a few important limitations, Tailwind can't fully support logical properties for example because `mb-8` could mean margin bottom or block. Any use case that requires styling one element based on another gets a bit hairy too.

Both of these can be technically worked around. Config may be able to disable existing margin/padding classes and replace them with a custom set, and the groups feature helps especially for simple cases of referencing other elements.

In my experience though, as soon as config is meaningful modified or you elan on the more obscure features for groups, pseudo selectors, etc. the learning curve has just been moved from the dev who doesn't know CSS to the dev who doesn't know Tailwind.

Re:Tailwind vs. Semantic CSS by Timon3 on Monday October 23, 2023 @09:48AM (#37985587)
Thank you for the correction!
Re:Tailwind vs. Semantic CSS by bryanrasmussen on Tuesday October 24, 2023 @03:21AM (#37995750)
that is also a thing, when I look at tailwind, having spent my time learning CSS why would I want to learn another syntax to help me do what I can already do, and probably do better.