I can’t wait for 2020, this is such a game changer for react native and it might also lead to synchronous/performant animation and gesture handling (kinda like react-native-reanimated and react-native-gesture-handler) and, most of all, doing a lot of the heavy lifting in the native side (network and api calls, vision/camera/audio/etc. libraries + offloading tasks to a bg thread) without slowing down the js thread. This would also mean that things like measuring views, getting x/y/width/height, scroll position and scroll related callbacks, setNativeProps etc. would be fast and synchronous!! No more wrapping things in promises and awaiting them. Native UI events will just fire and call our callbacks immediately 😭 Not to mention libraries like lottie, svg etc. will also be significantly faster. Maybe we can easily animate svg’s without all the hacks and workarounds. And lottie? You’ll no longer have to think about serialization and initializations. And for things like react-native-gl? Mapping gestures and taps directly? And native modules for AVFoudation and camera api’s? Bridging things like OpenCV?? The fact that you can easily bounce back and forth between native code and javascript will open up a whole new world of possibilities. Thank you for all the hard work in making react-native even better!
not going to be pretty but you can make a n/w request in the native code and cache it(before the js initialisation) and then get it from the rn code. Do it only if your app startup needs optimisation.
I can’t wait for 2020, this is such a game changer for react native and it might also lead to synchronous/performant animation and gesture handling (kinda like react-native-reanimated and react-native-gesture-handler) and, most of all, doing a lot of the heavy lifting in the native side (network and api calls, vision/camera/audio/etc. libraries + offloading tasks to a bg thread) without slowing down the js thread.
This would also mean that things like measuring views, getting x/y/width/height, scroll position and scroll related callbacks, setNativeProps etc. would be fast and synchronous!! No more wrapping things in promises and awaiting them. Native UI events will just fire and call our callbacks immediately 😭
Not to mention libraries like lottie, svg etc. will also be significantly faster. Maybe we can easily animate svg’s without all the hacks and workarounds. And lottie? You’ll no longer have to think about serialization and initializations.
And for things like react-native-gl? Mapping gestures and taps directly? And native modules for AVFoudation and camera api’s? Bridging things like OpenCV?? The fact that you can easily bounce back and forth between native code and javascript will open up a whole new world of possibilities.
Thank you for all the hard work in making react-native even better!
Great work to bring JSI, thats a game changer
Absolutely incredible! Good job!
I'm just trying to find the bridge Has anybody seen the bridge? Where's that confounded bridge! ; -)
@9:20
Amazing!
Has anyone found "David and Raul's talks"?
ruclips.net/video/FqMTXagEvHo/видео.html & ruclips.net/video/UcqRXTriUVI/видео.html
How can I fetch the network data before the js init as mentioned in the end of the talk? Any tutorial or blog about this? Thank you
Marcel Schulze you have to write a nativeModule for that sadly afaik (ie make a network request in java/swift and send it over to js)
not really make sense. that will move some logic from ReactNative code to irrelevant native code.
not going to be pretty but you can make a n/w request in the native code and cache it(before the js initialisation) and then get it from the rn code. Do it only if your app startup needs optimisation.
Can i get slides ?
Its Awesome
still waiting :/
It looks like...
You say ABC
and then BCA
and then CAB
until the timer of the talk alarms...
I am the one who disliked the video... :D