News for hackers. Stuff that matters.
Re:Retropiler: Java 8 Standard Library Backport for Android by pjmlp on Sunday May 07, 2017 @03:29PM (#14287123)
Not it is not, as I said read the AOSP commits.

Many methods don't have a full implementation, some classes have partial implementation and not every library class from OpenJDK is taken into Android.

Re:Retropiler: Java 8 Standard Library Backport for Android by bitmapbrother on Monday May 08, 2017 @12:16AM (#14289205)
I'm just confused as to why you think this is a problem? OpenJDK is an open source project and Google, or any other company, can fork it and trim as much undesirable fat as they wish. Additionally, as it has repeatedly been pointed out to you, Google does not call their fork Java not do they use any of the Java trademarks so your accusation that it fragments the language isn't true because it was never intended to be compatible with Java and the JVM. If Oracle has a problem with other companies forking OpenJDK then perhaps they should change the license for further releases or perhaps not make it "Open" anymore.
Re:Retropiler: Java 8 Standard Library Backport for Android by pjmlp on Monday May 08, 2017 @02:12AM (#14289598)
Because Google has broken Java portability, I cannot just take a random Java library and have it work on Android.

Thanks to Google now I need to search for Android Java libraries, instead of Java libraries.

Funny every time I search for Java on https://developer.android.com/develop/index.html I get several hundred results, and yet Google doesn't call their fork Java, go figure.

The difference, is that I don't live on Silicon Valley, I don't care about Google nor do I need to keep Android team happy to make a living.

What I care is that now I need to write two libraries instead of one.

Oracle (and Sun before) doesn't have a problem with companies that follow the license rules, there several commercial JDK vendors all of them nicely getting along with Oracle.

Re:Retropiler: Java 8 Standard Library Backport for Android by bitmapbrother on Monday May 08, 2017 @03:24AM (#14289863)
>Because Google has broken Java portability

Android was never intended to be used for Java portability so nothing has been broken.

>I cannot just take a random Java library and have it work on Android.

Android is not compatible with Java so why would you expect a random Java library, meant to work with Java, to work on Android?

>Thanks to Google now I need to search for Android Java libraries, instead of Java libraries.

A comprehensive list of libraries that work with Android has already been created so why would you need to look for Java libraries?

>Funny every time I search for Java on https://developer.android.com/develop/index.html I get several hundred results, and yet Google doesn't call their fork Java, go figure.

The Android SDK is a fork of the JDK. Did you expect them to rename every instance of the word "Java" to something else just for the sake of differentiation?

>What I care is that now I need to write two libraries instead of one.

I'm sure there are a plenty of libraries that work on either platform, but such is the nature of a fork. Support the platform you care about.

>Oracle (and Sun before) doesn't have a problem with companies that follow the license rules, there several commercial JDK vendors all of them nicely getting along with Oracle.

Google doesn't use the Oracle JDK they use the OpenJDK so why is a commercial license needed to use a forked version of an open source project?

Re:Retropiler: Java 8 Standard Library Backport for Android by pjmlp on Monday May 08, 2017 @04:11AM (#14290001)
Are there still open positions at the Android team?