3 ms·
That's accurate to the article but not accurate to modern RN or even most of Airbnb's reasoning when they switched. With JSI now you can get efficient access t
by hunterb123 4y ago
That's accurate to the article but not accurate to modern RN or even most of Airbnb's reasoning when they switched.
With JSI now you can get efficient access to native platform features. Before you were able to bridge pretty much any native feature with a native view or extension, but you were bottlenecked by the JS bridge. Nowadays you can use JSI for anything intensive.
As far as Airbnb, it was more they were trying to mix 80% native views with 20% RN views and they found they were doing more work than pure native. If you do mostly RN though you don't have that problem.
- zodester 4y ago> With JSI now you can get efficient access to native platform features. Before you were able to bridge pretty much any native feature with a native view or extension, but you were bottlenecked by the JS bridge. Nowadays you can use JSI for anything intensive. JSI indeed makes things more efficient, but you still have to maintain code to translate between native and JS.
- hunterb123 4y agoYes, but only the minimal to provide that specific native functionality, instead of a full blown native app. Unless you're doing something uncommon, there's most likely a 3rd party lib for that functionality. But yes, if you want to use a native platform feature that the standard lib doesn't expose of course you need native code either by you or someone else, that's the flexibility of React Native.