Alex

Just released react-native-columnar 🚀 A zero-copy columnar transport for React Native built around ArrayBuffer + TypedArrays. Benchmarks are pretty wild: • 27× faster at 100 rows • 94× faster at 500 rows • 121× faster at 1000 rows • 208× faster at 2000 rows

It's time to spill some secret sauce: How to actually build a good Keyboard experience for your #reactnative apps 👀

@adnansahinovich Something super interesting 👍

Built one of the fastest end-to-end encryption demos ever in React Native. ~0.8ms on-device MLS encryption powered by OpenMLS, Rust, and Nitro Modules. Zero-copy JSI. Native crypto performance. Full deep dive soon on blog.margelo.com

@BoazWith pushed a Memory management info

@pioner_dev If the public API hides it, user docs can stay light. I'd still keep an internal teardown note or test, because future bugs will come from maintainers forgetting that ownership rule.

Just released react-native-columnar 🚀 A zero-copy columnar transport for React Native built around ArrayBuffer + TypedArrays. Benchmarks are pretty wild: • 27× faster at 100 rows • 94× faster at 500 rows • 121× faster at 1000 rows • 208× faster at 2000 rows

@peterpme It won’t be the last one, will be part 2, then 3 , 😃

should i write a book called “The Last React Native Book in the Age of AI” and would it actually be the last one?

@BoazWith I will add it 👍

@BoazWith Do you think this is necessary ? since the user of the library will never touch this and works under the hood

@pioner_dev That destructor path is the part I'd document right next to the API. Cross-boundary ownership bugs are miserable when the rule only lives in the maintainer's head.

@peterpme if you return some data from the native side, and the data is like Array<{id: number, isActive: bool}>, and there are a lot of objects, you should try this solution, it's much faster

@pioner_dev interesting, what would i use this for?

@BoazWith When the last reference is destroyed, the class destructor is called and releases all resources

@pioner_dev Got it, shared_ptr on both sides makes ownership less scary. How are you handling teardown when JS drops the last reference first?

@BoazWith it will be destroyed when both sides no longer hold it

@pioner_dev Zero-copy is exactly where RN performance gets interesting. Did you have to change the API shape to keep ArrayBuffer ownership predictable?

Published github.com/pioner92/react…

Cooking something interesting around binary transports for React Native JSI

check it out github.com/pioner92/react…

@mrousavy @SamuelScheit the best solution (nitrogen schema generation )

@SamuelScheit @pioner_dev We're exploring different options, the most performant one could be a type-generated ORM via nitrogen

@mau_dev_uday Yeah, preparing a package 😃

@pioner_dev Hope it cooks well 🫠

@gabimoncha react-native-quick-base64: Yes, it has the same API. this -> react-native-quick-crypto I am not sure

@pioner_dev would this work as a drop-in replacement for react-native-quick-base64? both for react-native-buffer and react-native-quick-crypto?

Just published a new release of react-native-turbo-base64 with more optimizations 🚀

@SamuelScheit @mrousavy yep 😀

@pioner_dev @mrousavy oh lol @pioner_dev you also work for margelo, the world is a small place xD

@SamuelScheit yes, it always returns an array<{...}> which is slow, for example, if you query msg ids from the chat, you will have an array with objects with 1 property, id, I tested , it's too slow compared to a flat ArrayBuffer with ids

@pioner_dev Would be interesting to see the impact on db libraries. e.g. op-sqlite has something similar called executeRaw, which creates arrays instead of objects. #L207-L257" target="_blank" rel="nofollow noopener">github.com/OP-Engineering…

@BoazWith the benchmark code

@pioner_dev Yep, test it in the full render path too. The wrapper can look fast alone and still lose once JS reads it from a bunch of components.

@BoazWith In my benchmark, I read all properties, the same as from object , and the result is 90x faster