What is the reason for the instruction warning?
The library looks great! I wanted to ask what is the reason you don't recommend to use it as a standalone dependency?
Same question here, would be lovely to use thus
I wanted to ask what is the reason you don't recommend to use it as a standalone dependency?
I guess because usually something that involves parallelization or heavy computing you would write a native module for this. What are you trying to use RN Worklets for?
I wanted to ask what is the reason you don't recommend to use it as a standalone dependency?
I guess because usually something that involves parallelization or heavy computing you would write a native module for this. What are you trying to use RN Worklets for?
In our case we use RealmJS. We wrote a sync script that does paginated API Calls and store it inside RealmJS, our biggest customer has 800.000k records, we do 1000 per page so we would like to run this on a separate js worklet, right now we use startBackgroundTaskWithName, but JS is still suffering. I tought about building a native module, but then we have to recreate the ios and java schemas for the realm android and realm ios.
Yea well maybe in this case it makes sense. ๐
I have a similar use case. We are using RealmJS and we'd like to be able to load ~25k events from the database and do some statistical analysis and then show that data to the user.
Love to help/discuss on this matter @mrousavy . Would be nice to give RN performance for side tasks that are normally to intense ๐ช๐ป๐ช๐ป maybe @aks427 can also elaborate.
Try react-native-worklets-core - if it works for you and is more performant, then that's great :)