6 ms·
This is the direction React Native is heading, with Fabric Native Components[1] and Turbo Native Modules[2]. On the development side, you have JavaScript, the l
by cthulberg 3y ago
This is the direction React Native is heading, with Fabric Native Components[1] and Turbo Native Modules[2]. On the development side, you have JavaScript, the language we all love to hate and hate to love, with its vast ecosystem of readily available libraries that are well-documented and used daily by billions of people. On the functionality side, you have access to native code, which speeds up and lightens the workload, making the app performant.
[1] https://reactnative.dev/docs/the-new-architecture/pillars-fabric-components https://reactnative.dev/docs/the-new-architecture/pillars-fa...
[2] https://reactnative.dev/docs/the-new-architecture/pillars-turbomodules https://reactnative.dev/docs/the-new-architecture/pillars-tu...
- pjmlp 3y agoThanks, I wasn't aware of them.
- delfinom 3y agoLol, amazing to see history repeat itself over and over again
- pjmlp 3y agoIndeed back in the dotcom wave, the startup I joined was making our own flavour of AOLServer. Now in some projects, I am basically doing the same, with the difference that now I am using JavaScript instead of Tcl, and C++ instead of C for the native side. At least now I have a JIT in the box.