3 ms·
I'm going the opposite way and switching from CSS-in-JS to Tailwind. While I like the css-in-js way of doing things, React seems to be moving away from runtime
by hakanderyal 4y ago
I'm going the opposite way and switching from CSS-in-JS to Tailwind.
While I like the css-in-js way of doing things, React seems to be moving away from runtime css generation, and I'm not sure the ecosystem will catch up (and I'm tired of playing catch up).
Sticking to CSS guarantees you won't have any compatibility problems.
- redbar0n 4y ago> Sticking to CSS guarantees you won't have any compatibility problems. Unless you attempt to go cross-platform.. There are many attempts at getting CSS working on React Native for instance, and many have various compatibility problems (especially as they need to keep up with the evolving CSS spec). But if you do go cross-platform, then something like Tamagui is probably a better bet than trying to replicate CSS. You could also try Nativewind, to get the Tailwind benefits (and limitations, like lack of support for animations).
- hakanderyal 4y agoI don't need native and web compatibility, so no problems on that front. Tamagui is on my radar, but it's too new for me to give it a try with my limited time budget.