gradle-native VS open-native

It is theoretically possible to support Conan in Gradle without any changes to its core. I have been experimenting on and off to demonstrate the support and add it as a feature to Nokee. You can follow the project on GitHub to stay up-to-date (https://github.com/nokeedev/gradle-native).

What they decided to do is really quite strange. Something like Capacitor makes much more sense but they said they wanted access to React Native libraries... I hope https://github.com/OpenNative/open-native can address their requirements in the future. It's goal is to make things like React Native native modules work across frameworks (e.g., react native libraries working in capacitor and native script)

You can now use React Native plugins within NativeScript projects through the Open Native effort and it's only a matter of time before NativeScript can be used where the React Native community sees fit.

As NativeScript offers a cross-platform UI abstraction, you can build your whole UI without writing platform-specific code. There are often cross-platform plugins available to avoid having to write any platform-specific code, and in fact we’ve recently built Open Native to allow you to use React Native native modules in NativeScript apps (Svelte Native included). But even when there is no plugin available, writing the native code is a breeze, as it has full TypeScript typings and you can pass real native values back and forth between native and JS rather than just JSON-serialisable ones. It’s really quite incredible!

Open Native is the long overdue Rosetta Stone that allows native modules to be used cross-ecosystem. It handles all the necessary auto-linking, type marshalling and API-binding to allow you to choose the highest quality native module for your project, no matter what ecosystem it comes from.

The complete steps to run the benchmarks are available in the main repo: https://github.com/OpenNative/open-native/blob/main/benchmark.md