Comment by skybrian
19 hours ago
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?
19 hours ago
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?
I mean just go over v4.x.x release changelogs [0].
The "web platform" is evolving at a decent pace in general [1][2]. You can sometimes do the same thing in 50 different ways (thanks to the breadth of css features and js apis and backwards compatibility), but there may be a much more elegant and robust solution on the horizon and when it hits the baseline, chances are it would likely lead to a simpler framework codebase and/or shrinked output if integrated... and therefore such a feature should be integrated. Now do this a zillion times over the life of the project. You have to keep up.
Less hacks, less code, smaller outputs.
And THEN you have all the bug reports and new feature requests.
And THEN you're supposed to work on something built on top of Tailwind that you can actually sell so you have something to eat tomorrow.
[0]: https://github.com/tailwindlabs/tailwindcss/releases
[1]: https://web.dev/blog
[2]: https://developer.chrome.com/new
If the old way didn't break, it's not true that you have to change it. You can ignore the new stuff if you want to.