Are you saying the www consortium should be paying to keep Tailwind development and maintenance going? The css standard is not the same as a usable library of components.
> others who deem Tailwind valuable enough will continue to maintain it.
We have seen several examples in the last couple of years where this is simply not true enough. There are multiple open source projects that do not receive enough TLC.
If my company relies on an open source project and it isn't being maintained, I can either ask my company to start maintaining it or find something else or accept the risk of a an unmaintained project.
The problem here is that the w3c sucks a fat one, and they've failed to build software specs that don't require an ecosystem thousands of libraries to make using CSS, etc. simple or efficient.
In the case of CSS, we already have that:
https://www.w3.org/Style/CSS/Overview.en.html