Really difficult to use realm.js with react.

1. snapshot not deep frozed /immutable. // 3years ago you say you areing working toward it 2.even no toObject or toArray common function in other database. 3.no equal or is function to compare two object or collection is updated or not. As we all know in react we need to refine code in shouldComponentUpdate to improve performance,without this funciton it is really very difficult to use realm.js. 4.debug mode in react-native failure because of realm.js last for a long time never really solved.

[Genhain]

A performant Deep cloning snapshot would be a lifesaver. Currently having issues with a FlatList component because any changes made get handled by a realm listener and then forwarded to the FlatList then when i try to memoize or use shouldComponentUpdate to reduce unchanged prop render, the current prop and next prop are identical. So the fix for this is to make a deep clone of each object returned from the listener and then pass it to the FlatList , although this works on a small scale like in this little repo I have here, For my current project which handled a list with up to 100,000 of items with more complex UI, the cloning can take quite a while…if I had access to threads or background workers this would be a small pain, but i do not, so it is a big pain.

[Piero87]

@fronck Thank you for your suggestion, I have read the repository and it seems very very interesting to me, it’s an upcoming package? what is its status?? alpha beta?