undefined | Better HN

0 pointspjmlp9y ago0 comments

Actually 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-review.googlesource.com/#/q/status:open+open...

0 comments

3 comments · 1 top-level

kllrnohj9y ago· 2 in thread

> but achieving feature parity is certainly not something they care about.

[citation needed]

what is missing?

pjmlpOP9y ago

So 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.

kllrnohj9y ago

Swing & JavaFX are not part of the JCL. Those are addon libraries.

NIO: 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/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/Met...

j / k navigate · click thread line to collapse