| ▲ | bob1029 a day ago |
| > we do probably need some kind of industry organization to maintain these things. In the case of CSS, we already have that: https://www.w3.org/Style/CSS/Overview.en.html |
|
| ▲ | mrgoldenbrown a day ago | parent | next [-] |
| 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. |
| |
| ▲ | aurareturn 19 hours ago | parent | next [-] | | Tailwind is open source. Anyone can contribute to it, including an LLM. If the founder of Tailwind quits on it, others who deem Tailwind valuable enough will continue to maintain it. | | |
| ▲ | HumanOstrich 2 hours ago | parent | next [-] | | You're just parroting what you've heard. The reality of continuing an abandoned project is not that simple. | |
| ▲ | zephen 16 hours ago | parent | prev [-] | | > 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. | | |
| ▲ | aurareturn 9 hours ago | parent | next [-] | | Then it isn't important enough to people. 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. | |
| ▲ | 14 hours ago | parent | prev [-] | | [deleted] |
|
| |
| ▲ | 14 hours ago | parent | prev [-] | | [deleted] |
|
|
| ▲ | terribleidea 20 hours ago | parent | prev [-] |
| 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. |
