| ▲ | Culonavirus 18 hours ago | ||||||||||||||||
> How much money do you really need to maintain a CSS library? Seems to me like Tailwind is a relatively complex beast covering a lot of ground, not to mention that web browsers are living/evergreen projects that are costantly moving forward, and so the lib needs frequent updates. I don't think you can avoid this (just by the nature of the project). You also need to be a css expert who follows the browser and feature development closely on top of having an excellent grasp of js/ts and the build (lightining css, vite...) ecosystem. I mean ... A few excellent engineers and a designer is probably just the bare minimum to keep Tailwind maintained. | |||||||||||||||||
| ▲ | skybrian 15 hours ago | parent [-] | ||||||||||||||||
If browsers are breaking old CSS, making new releases necessary, then that seems like a bad situation. I thought browsers were good at maintaining backward compatibility? Not so for Tailwind? | |||||||||||||||||
| |||||||||||||||||