3 ms·
That's not the point. Running in the JVM is the most performant way to access Android's APIs. That's "native".
by orbitur 9y ago
That's not the point. Running in the JVM is the most performant way to access Android's APIs. That's "native".
- Turing_Machine 9y agoWhat if the JavaScript is compiled to JVM opcodes? I guess I don't see your point here. A Java compiler takes Java code and compiles it to JVM opcodes. Presumably this package (I haven't looked at the details, so could be wrong here) takes JavaScript code and compiles it to JVM opcodes. I see no prima facie reason to assume that one would be more "performant" than the other. That's the whole idea behind things like LLVM and CLR, right?
- iOSGuy 9y agoIt doesn’t compile it to JVM, it runs a JS engine, and then passes some calls into the native side over an asynchronous bridge, and the native code then builds native views at runtime. It’s a middle ground, and it’s super useful in some cases, and super dumb in others. It’s not a silver bullet, it doesn’t solve all the problems, but it has some good use cases.