|
|
|
|
|
by BitMastro
4361 days ago
|
|
You're comparing apples and oranges, Apple had the privilege of choosing its own hardware and programming language. For android they went for java because of popularity, and everyone can use it on their own hardware. So you have a java based language running on ARM, x86 and MIPS, what would you choose? A proven approach like JIT VM or AOT? |
|
Google and Apple both used already existing languages and adapted existing kernels. If you're saying that Apple didn't use an existing language or that Google didn't have the option of being more restrictive with hardware, then you are wrong on both counts. Google made choices which turned out to be worse for users over a certain timeframe. They were more attractive to vendors and manufacturers, however.
> For android they went for java because of popularity, and everyone can use it on their own hardware.
Google was optimizing for programer popularity, not user experience.
> So you have a java based language running on ARM, x86 and MIPS, what would you choose? A proven approach like JIT VM or AOT?
If you're going to go with what's more proven with constrained resources, then you'd go AOT. If you're trying to optimize for UX and lag, but high level enough for rapid development, then AOT with reference counting GC.