tailwindcss

You can, but it goes against Tailwind's philosophy. It used to be explicitly discouraged here[0] (see this 2022 GH comment[1]), but now they just don't mention it. [0] https://tailwindcss.com/docs/styling-with-utility-classes#ma... [1] https://github.com/tailwindlabs/tailwindcss/discussions/7651...

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://gi

TIL they use Bun: https://github.com/tailwindlabs/tailwindcss/commit/1e949af9a...

One could compare the main branch against its state from one year ago to find out if the core product justifies this scale. I would say that, more likely than not, it isn't. https://github.com/tailwindlabs/tailwindcss/compare/main%40%...

Sounds like 3: https://github.com/tailwindlabs/tailwindcss/discussions/1467...

https://github.com/tailwindlabs/tailwindcss/discussions/1467... In this comment, he says that he had to lay off 3 people. Not sure if this means it was him+4engs and now it’s just him+1eng or if he’s including himself and he’s working alone now. But either way, can’t be fun

More details: https://github.com/tailwindlabs/tailwindcss/discussions/1467... https://x.com/adamwathan/status/2008909129591443925 https://adams-morning-walk.transistor.fm/episodes/we-had-six...