Show HN: Tailwind DX – A DevTools Extension for Tailwind CSS Developers

gimli.app

24 points·gimliapp··6 comments

1. Destroy DX by introducing utility classes approach in Tailwind 2. Try to fix it by introducing Chrome extension

I really appreciate the work on that tool, but after using Tailwind for 6 months I really don't like it. Of course you can quickly hack something using it, but the code quickly becomes unmaintanable... I wouldn't recommend it to anyone.

That's web development, things move in circles :)

I have really been trying to get into tailwind.

The more I learn about it, the more I fail to see why it would offer any sort addition to just using CSS /SCSS/SASS.

Can anyone elaborate on why tailwind is preferable to a CSS preprocessor?

I personally find it hard to maintain "normal" CSS. Especially when things change a lot. That first version of a site might be great. But I honestly never seen an old site with good maintainable CSS, it seems developers just give up after a while.

That said, I don't think Tailwind is the solution for everything. Tailwind DX/Gimli is created with styling in the Shadow DOM, which works great. For more regular websites I would use Tailwind. But for more App like solutions I would preferably put the styling scoped within components.

Thats really cool and sounds useful. Debugging tailwind in the dev console is not much fun. Thanks! :)

cool, I like it

Reply on news.ycombinator.com