3 ms·
Yes, but we found plenty of bugs. Fixed some (e.g. in TrueSheet). It is drastically faster, but I won't call it a "game changer". It's great for us because we
by cyberax 1y ago
Yes, but we found plenty of bugs. Fixed some (e.g. in TrueSheet). It is drastically faster, but I won't call it a "game changer".
It's great for us because we have native code modules, and seamless Turbo Modules are nice (you _can_ use them with the old arch, but it requires some jumping through hoops).
As for reanimated, I would just stay away from it entirely. Way too many layering violations for my taste.
- tcoff91 1y agoIt’s not so much the performance that has me excited, just the synchronous vs asynchronous communication with the renderer.
- cyberax 1y agoIt has its own problems... Since the async round-trip is gone, you can end up with rendering happening too _early_. The rendering is also not truly synchronous, you can't resize graphical surfaces from the JS thread. You still need to do a round-trip to the platform UI thread. So for example, React Native WebGPU misrenders an image when you rotate the screen because of that. The rendering callback ends up running before the surface has the chance to get resized. I've also seen that with other libraries that mix native rendering. I'm pretty sure reanimated is also susceptible to this.