i’m not confident we’ll necessarily want to build this directly into the product (tradeoffs to consider) but the fact that it can be done in the ecosystem is awesome. let the ecosystem cook
RE:
honestly this makes me think i’d actually like to see an RSC-like twist on the Reanimated model.
the original idea that inspired RSC (client/server serialization split, components on both sides) was actually an early proposal for multithreaded React (Native) [github.com/reactjs/reac...](
is there some good way to gain intuition about the cost of Reanimated worklets? in particular it feels like there is a cost to referencing functions from them — even if those functions have stable identity on the JS thread. how to think about this?
does anyone understand what renderToHardwareTextureAndroid actually do? if i have a few nested animated views, all with static content, but each has its transform independently animated, would it help to add this prop to all of them? either of them? outermost one? innermost one?
