> Do you think this looks maintainable? I guess that depends. Compared to what? Again, show me the equivalent widget implemented some other way and we can hav

> Do you think this looks maintainable? I guess that depends. Compared to what? Again, show me the equivalent widget implemented some other way and we can have a useful discussion. Having spent a little time experimenting with tailwind for prototypes in the past, I can understand what that snippet is doing pretty easily. Having spent a lot more time writing vanilla HTML/CSS, I can immediately imagine all of the ways the vanilla version would be a nightmare, or at least take far longer to build “properly”. Tailwind is a fascinating project because it seems to either make sense to people or it seems to deeply offend them. For whatever reason, I’m able to build things with tailwind after just a few hours of use that I could never accomplish from scratch (or with some popular CSS frameworks for that matter) after years of hacking on HTML/CSS. 15 minutes getting familiar with the class naming conventions makes all of this seem far less scary. And it’s worth considering the variety of use cases a framework like this is useful for. Maintainability means very different things depending on context, team, and what kind of thing you’re building.