What working with Tailwind CSS every day for 2 years looks like

Re:What working with Tailwind CSS every day for 2 years look... by zupa-hu on Tuesday November 29, 2022 @02:14PM (#33791815)

I think Tailwind is great but I agree with many of the issues raised.

I desperately needed a _language_ instead of a framework back when Tailwind was still a framework. As I could not get any response from them, I ended up rolling my own called Turbo CSS - this was like 2 years before their compiled version came out. Take a look if you want to consider alternatives.

https://developer.boomla.com/turbo-css

I'd compare the two as Tailwind being primarily a framework, a language second, while Turbo is a language first. For example, in Turbo you write libraries and reference class names in libraries via `my.btn` instead of polluting the global namespace. It also has first class support for classes, like you can do `hover:my.btn`, which Tailwind doesn't support (to my best of knowledge, it definitely didn't back then). Also, Turbo has zero global side-effects, which makes it great if you don't control the entire codebase (think CSS reset).

[ Parent | on HN ]

Re:What working with Tailwind CSS every day for 2 years look... by themosaad on Tuesday November 29, 2022 @06:04PM (#33794635)

Great work scratching your own itch! Not as easy addition to the workflow as it doesn't have a CLI but I think that's intentional or not a priority for you.

I backed out from maintaining a big Tailwind CSS plugin let alone create my own solution.

Similar to React, I don't think Tailwind CSS is easy to replace regardless of the slightly better alternatives that exist or might popup up due to its established community.

[ Parent | on HN ]