Okay, then: 1) Switch to Go as Android platform flagship language
2) Stick with the Go ARM native code compiler approach 3) Enhance Go to support versionable dynamic link libraries (similar to Adobe Flash Player Runtime Shared Libraries feature) The last item means that each Go app would not need to redundantly statically link in the Go runtime libaries. The support of dynamic linking with versioning means that the Go runtime libraries could evolved over time and a Go app when launched would dynamically link to the version that was compiled with at app build time. Android phones would cache all these Go runtime library versions. There would be no dependence on VM technology with this approach but the runtime, having sophisticated features such as garbage collected memory management, could still be efficiently shared on a relatively constrained device. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to javapo...@googlegroups.com. To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
