Tamagui seems to hype performance but it seems like it’s adds a lot of complexity to optimize web styles which are already very fast. The difference when talking about native (not react-native on web) is tiny IIRC
The great thing about it is that it basically gives you the benefits of CSS-in-JS on the web, but without the downsides, since it compiles away to atomic CSS (even ternaries!).
It’s true that it’s marginally less performant than vanilla React Native (within 10%, looks like 1.9%):
And for that tiny difference on native, you in return get close to 100% code sharing between native and web. As opposed to writing vanilla React Native and then writing it again for vanilla React.
you get very similar code sharing with react-native-web and StyleSheet.create…
I guess i am just much more interested in making the native side faster. I have never had issues making something in React Native and then having the web side be the slow part.
Web is the much more performance sensitive side, where it improves most.
If you do pseudo styles or responsive styles with RNW your web app will absolutely tank in all metrics, runtime/lighthouse/load/layout. Tamagui fixes all four. That normally prevents code share for anything more than small apps or totally performance insensitive use cases, otherwise Tamagui makes a big difference.
