[josecodea]

In which case one has to wonder if we need tailwind at all anymore. To me, years ago, tailwind was a great sell as a tool to work faster by typing less. The tradeoff is that the "inline styles" look awful and become a mess real quickly when too many of them are placed together (so and so has precedence or whatever, a media query for each single property, constantly translating between CSS and tailwind equivalent, etc).

Now? Well, AI solves the entire issue of time taken typing. Classnames always looked cleaner too. Additionally CSS doesn't lag behind Browser features and comes with the full power of the language.

Why bother with Tailwind anymore whatsoever?

They were extremely lucky that AI picked up tailwind to keep it relevant, they should be keeping up with the times if they want to stay relevant. Instead their actions are those of someone that is cowering in fear, making sure that they can put the last of the revenue into the coffer. (reject PR because they don't want AI to do better with tailwind while firing engineers, not to mention the big tantrum).

Lets go back to actual CSS, it is easier to read anyway, it's now a modern tool with variables and all that, there's no longer a need to dumb it down.

Besides, if I wanted to pay for pre-made components, I would go with DaisyUI which is agnostic to the frontend framework, unlike the paid components from tailwindLabs, which strictly require you use one of the javascript frameworks.