技術ネタ満載の YCombinator の運営する「Hacker News」で昨日から話題になっています.
Google confirms next Android version won’t use Oracle’s proprietary Java APIs | Hacker News
このへん素人目にも想像できるのは「著作権料を払いたくない」という理由.
So in order for Google to avoid paying that royalty going forward they need to move to OpenJDK quickly with their next release, with the belief that using Oracle's GPL JDK implementation also gives them a license to the API (which is somehow separately copyrightable? The Federal Circuit is a mess).
ここらの適用範囲などの法律の話は金額のわりに明快でなく庶民には分かりづらい.
実際, 開発中のソースコードではどのようになってきているのか.
Mysterious Android codebase commit | Hacker News
This diff is more explicit about what's going on:
https://android.googlesource.com/platform/libcore.git/+/aab9...
Change dependency from libart -> libopenjdkjvm.
There are also diffs adding lambda support, tweaking various classes for compatibility with applications that use reflection to access internal capabilities, and fixing lots OpenJDK compatibility bugs.
確かに, OpenJDK に移行してるようにも見えるが.
In the context of the recent juniper attack where some unauthorized code was committed without anybody noticing for years, it seems like it would be easy to hide a backdoor in such a big commit.
How do you go about checking the integrity of the code when you have so many files?
8902 files were changed, most added, and the commit says it's just importing openJDK files. Is there anybody checking that the source file imported haven't been modified to include some kind of backdoor?
はっきり「OpenJDKに移行を進めている」とは言い切れないのか.
WEBでは見づらいのでアプリで.