3 ms·
I was already quite puzzled about why Google would make the apparently quite significant change (millions of lines of code will need to be rewritten according t
by mtgx 11y ago
I was already quite puzzled about why Google would make the apparently quite significant change (millions of lines of code will need to be rewritten according to this post, too) and still stick with Java, instead of going Go or something else (even if it would be even harder to do it). But this article made me go "WTF are you thinking Google?!"
The only explanation I can come up so far (also in light of the recent partnership between Google, Oracle and HPE for RISC-V) is that Google kind of "admitted" that it's not supposed to use Dalvik without paying Oracle, so they went to Oracle and "reached a deal" - Google won't have to pay anything to Oracle, but Oracle gets to control a large portion of Android now, and will also likely get to be paid by Samsung, LG and all the major OEMs who will pay Oracle for a "custom proprietary license" so they can modify pieces of Android.
As the article concludes, this seems like a major win for Oracle and a big FU Android users! from Google. Can we even trust Oracle won't introduce some "accidental" goto fail-like backdoors in Android code, now? Oracle code is already full of security bugs, so nobody would even bat an eye - just Oracle doing Oracley things.
- on_and_off 11y agothe whole article is insane and nonsensical. Swing is not part of AOSP, ART is still the Runtime. Oracle still does not have any influence on the platform. Google has just switched to a better code base. OpenJdk did not exist yet when They chose Harmony and OpenJdk will allow them to use Java 8 features.