5 ms·
> speaking of Android: How about switching to the JVM/OpenJDK to keep pace with modern Java? They did that already. https://arstechnica.com/tech-policy/2016/01
by kllrnohj 10y ago
> speaking of Android: How about switching to the JVM/OpenJDK to keep pace with modern Java?
They did that already. https://arstechnica.com/tech-policy/2016/01/android-n-switches-to-openjdk-google-tells-oracle-it-is-protected-by-the-gpl/ https://arstechnica.com/tech-policy/2016/01/android-n-switch...
Well, they switched the library to OpenJDK. The runtime is still ART, but that's probably for the best as the runtime balance decisions made by hotspot are definitely not suitable for phones, and ART is pretty good these days anyway.
And you can use Java 8 stuff: https://developer.android.com/studio/preview/features/java8-support.html https://developer.android.com/studio/preview/features/java8-... some of which is even fully backwards compatible (like lambdas)
> Also, how about using cgroups instead of the custom security model? Maybe we could get reuse out of Google's security patches for Linux, and they could benefit more from the community.
Android has always used cgroups. cgroups are not a security mechanism, though, it's for resource allocation.
Regardless Android makes use of cgroups, cpusets, selinux, etc... That's all unrelated to the permission model, though, which more or less doesn't exist on desktop platforms.
- pjmlp 10y agoActually the reality is a bit different than those marketing articles. They started to cherry pick library implementations from OpenJDK, but achieving feature parity is certainly not something they care about. Anyone can easily check the AOSP commits to see exactly that. https://android.googlesource.com/platform/libcore/ https://android.googlesource.com/platform/libcore/ https://android-review.googlesource.com/#/q/status:open+openjdk https://android-review.googlesource.com/#/q/status:open+open...
- kllrnohj 10y ago> but achieving feature parity is certainly not something they care about. [citation needed] what is missing?
- deleted 10y ago[deleted]
- pjmlp 10y agoSo many things. - Swing - JavaFX - NIO and NIO2 - invoke dynamic - method handles Are a few that come to my mind, but basically besides from what was left out of Java 6 libraries, almost everything that was introduced in Java 7 and 8.
- kllrnohj 10y agoSwing & JavaFX are not part of the JCL. Those are addon libraries. NIO: https://developer.android.com/reference/java/nio/package-summary.html https://developer.android.com/reference/java/nio/package-sum... "added in API 1" As in, it's been there since forever. What are you referring to specifically? NIO2: https://developer.android.com/reference/java/nio/file/package-summary.html https://developer.android.com/reference/java/nio/file/packag... Invoke dynamic: is a runtime/bytecode thing, not part of the library. The actual feature, lambdas, works just fine on Andorid Method handles: https://developer.android.com/reference/java/lang/invoke/MethodHandle.html https://developer.android.com/reference/java/lang/invoke/Met...