4 ms·
Most such attempts run up against the particular way that a Java-like runtime is used in Android: The max heap size is tiny compared to desktop, nevermind serve
by Zigurd 11y ago
Most such attempts run up against the particular way that a Java-like runtime is used in Android: The max heap size is tiny compared to desktop, nevermind server Java defaults. You have LOTS of instances of the runtime that depend on the Zygote and copy-on-write so as not to eat all of memory. Component lifecycle has to be handled or you will hate life. Inter-component and inter-process communication and cooperation are deeply rooted in the Android architecture. Lots of the Android OS is built in Java, and takes advantage of Android's runtime limitations and capabilities. In other words, unless you replace Java with another JVM language, you are implying a different OS, not Android with a "better" language.
- vvanders 11y agoLots of truth here, a new language isn't going to solve things. React Native is probably the closest that you're going to get.