3 ms·
The difference here is that Google was not trying to ensure interoperability with anything, they just wanted to mimic Java to attract developers. Is that true?
by geofft 11y ago
The difference here is that Google was not trying to ensure interoperability with anything, they just wanted to mimic Java to attract developers.
Is that true? Can't you use several Java packages (at least in source form), IDEs, etc. with Android?
- toyg 11y agoSorry, i removed that bit from my comment because I thought it was a bit too biased, and tbh I wasn't paying too much attention to Android when it started, so I might be wrong and everything. This said, IIUC, the point is that they did not build Android specifically to achieve interoperability with, say, Eclipse; they built Android in Java for whatever reason (including attracting developers), and when they realised they couldn't use the JVM because of commercial issues, they swapped it with Dalvik (which may or may not be a complete clean-room JVM reimplementation). So it's not exactly in the same bucket as "we built this because existing tooling expected it this way"; it's more like "we built something, then had to rewrite the bits underneath because we realised we couldn't use them", a different scenario.
- c22 11y agoMy understanding is Android already used Java when Google acquired it.
- toyg 11y agoYeah, but the switch to Dalvik (which is where the trouble starts) was done under Google. If they had just thrashed out an agreement with Sun (which would have been much much cheaper than dealing with Oracle will ever be...), they could have continued using the official mobile-oriented JVM, likely influencing its development as well; but first they dragged their feet and then they thought they'd just rewrite the whole thing so they could claim originality and independence, and here we are.