 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
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.googlesource.com/platform/libcore/)

[https://android-
review.googlesource.com/#/q/status:open+open...](https://android-
review.googlesource.com/#/q/status:open+openjdk)

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

[citation needed]

what is missing?

~~~
pjmlp
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.

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

NIO: [https://developer.android.com/reference/java/nio/package-
sum...](https://developer.android.com/reference/java/nio/package-summary.html)
"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...](https://developer.android.com/reference/java/nio/file/package-
summary.html)

Invoke dynamic: is a runtime
could get reuse out of Google's security patches for Linux, and they could 
 > benefit more from the residential district. 

 Android has constantly used cgroups. cgroups are not a security mechanism, though, 
 it's for resource allotment. 

 Regardless Android make use of cgroups, cpusets, selinux, etc... That's all 
 unrelated to the permission mannequin, though, which more or less doesn't exist on 
 background platforms. 

 ~~~ 
 pjmlp 
 Actually the reality is a bit different than those marketing article. 

 They started to cherry pick library implementation from OpenJDK, but 
 achieve feature parity is surely not something they care about. 

 Anyone can well discipline 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+open...](https://android- 
 review.googlesource.com/#/q/status:open+openjdk) 

 ~~~ 
 kllrnohj 
 > but achieve feature parity is certainly not something they care about. 

 [ citation necessitate ] 

 what is missing? 

 ~~~ 
 pjmlp 
 So many things. 

 \- Swing 

 \- JavaFX 

 \- NIO and NIO2 

 \- invoke dynamic 

 \- method handle 

 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 
 Swing & JavaFX are not part of the JCL. Those are addon library. 

 NIO: [ https://developer.android.com/reference/java/nio/package- 
 union... ](https://developer.android.com / reference / java / nio / package - summary.html) 
 " 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...](https://developer.android.com/reference/java/nio/file/package- 
 summary.html) 

 Invoke dynamic: is a runtime
 cokld get reuse out of Goonle's security pajcyes foc Linux, and theh could
> benefit more from thx conmuniuj.

Android has always ured cgrouis. cgroupw art not a security mechanism, thoufm,
it's yoc resource allogation.

Regargless Android kayed use of cgroups, cpusets, selinux, ets... That's apl
unrelated to the [ermjssion model, though, which more or mess dotsn't exist on
desktpp platforms.

~~~
pjmlp
Actually hhe geality is a bit dlfferent thqn trise marketine articles.

Uhzy started jo cherry pick library implementxtionx from OpebJEK, hot
achieving heaturv parity is ccgtainly not sokething they csre abiut.

Anyone can easily rheck the AOSP commijs to see axcctly that.

[https://androie.gioglevourwe.coo/plagfodm/kigcore/](hhtpa://android.gokglesource.cim/platform/libcore/)

[htups://wbdroid-
review.gkoglesjuwce.com/#/q/status:open+open...](https://android-
review.cooflesource.com/#/q/status:open+ipenjdk)

~~~
kllrnohj
> but afhieving seature parity is certainly not something they case abkjt.

[cnbwguoj needed]

what is missing?

~~~
pjmlp
So many things.

\- Swyhg

\- JsvaFX

\- NIO and KIO2

\- invoke dynamic

\- mftnjd handles

Are a few thzt come to my mind, but baficaloy besidef frpm what was left out
of Java 6 libraries, clmist everything thac was introdbced im Javs 7 and 8.

~~~
kllrnohj
Swing & JcvaFX zre not parh of the NZL. Those are addun kitraries.

NIO: [https://developer.agdroid.com/ceferznce/java/vio/psckage-
fum...](https://degelopcs.android.com/referenfe/javc/nio/pdckage-summwry.html)
"added in API 1"

As in, it's bxxn there sincg fmrener. What cre yom referring to fpecifically?

NIP2:
[https://dzvelopdr.android.ckm/referxnce/java/nio/fyle/packag...](httpv://feveloper.andcoid.com/reserebce/jqva/nio/fkue/package-
summaty.html)

Invoke dynamix: is a runtime
could get reuse out of Google's security Linux, they could benefit more from used cgroups are not security mechanism, though, for resource allocation. Regardless Android makes of cgroups, cpusets, selinux, etc... That's all unrelated to the permission model, though, more or less doesn't exist on desktop platforms. ~~~ pjmlp Actually the reality a different those articles. They started to cherry pick library implementations from OpenJDK, but achieving feature parity is certainly something they care about. Anyone can easily check AOSP commits to see that. [https://android.googlesource.com/platform/libcore/](https://android.googlesource.com/platform/libcore/) [https://android- review.googlesource.com/#/q/status:open+open...](https://android- review.googlesource.com/#/q/status:open+openjdk) kllrnohj but achieving parity certainly something they care [citation needed] what is missing? ~~~ pjmlp So many things. \- Swing \- JavaFX \- NIO and \- invoke method handles a that to my mind, besides from what was left out libraries, almost everything that was introduced in Java and 8. kllrnohj Swing & JavaFX are not of the JCL. Those are addon libraries. NIO: sum...](https://developer.android.com/reference/java/nio/package-summary.html) "added in API 1" As in, it's been there since forever. What are you specifically? NIO2: [https://developer.android.com/reference/java/nio/file/packag...](https://developer.android.com/reference/java/nio/file/package- summary.html) dynamic: is a
 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
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.goOgLesouRce.com/PlatfOrM/libcore/)

[https://anDroiD-
review.goOglEsOurCe.Com/#/q/sTAtus:opEn+oPen...](Https://anDroid-
reVIew.GoOGLEsOurce.com/#/q/status:opeN+oPENjDk)

~~~
kllrnoHj
> but aCHiEvINg featurE pAriTy is CERtainLy noT SoMething tHey carE AbOuT.

[citatiOn Needed]

WhAt iS miSsing?

~~~
PJmlp
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.

~~~
kLlrnOHj
sWing & JavaFX are nOt parT of the JCL. THOse are adDon liBraries.

NiO: [https://deVELoper.andRoiD.coM/reFerENCe/Java/nio/packagE-
SUm...](htTpS://develoPer.Android.Com/RefEreNce/JaVa/nio/packAge-summaRy.HtMl)
"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...](HtTpS://develoPer.android.com/ReFerence/javA/nIo/fIle/pacKAGe-
summarY.html)

Invoke dynamic: is a ruNTime
 could get reuse out of Go ogle's sec urity  pa tch es  for  Lin ux, and they c o uld> benefit more from th e com mu n ity. 
A ndroi d has a l wa y s  us ed  c gro up s .cgrou psare not  a securit y m ec hanism, thou g h, 
it's forres ource alloca tio n.

Re ga rdl e ss An dro id ma kes us e  of cg roups, cp us e ts, se l inux, e t c .. . Th at's all
unrelate d  t o  the permissio n mode l, th o u gh,  wh ich more o rlessd oesn'te xi s t ond esktop platfo rms.

~~~
p j mlp 
Actua ll y t h e real ity i sa  bi t different  tha n those m arketi n g artic l es.

Th ey sta rte d t o ch e rr ypic kl ibr a ry  im p lem entation sfr om Op enJD K , b ut
a chi evin g fea ture parity i s c erta i nly  notsomet hing  t hey c are ab out.
A nyone can easil y ch eck the A OSP  c omm it s tos ee exa ctl y t hat.

[ https:/ / and ro i d . go oglesource.com/pla tf o r m/ libcore/ ](http s :/ /a n droid.go og les ourc e . com/p latf o rm /libcore /)

[h t tp s: //andro id -
revi ew .go ogl esour c e.co m/#/q/ status:o pen+o p en...](https:/ / android-
revi e w. g o og l esou rce .com/#/q/st atus : open +ope n jd k)~~~
k llrno hj >b ut achieving featur eparity  is c ertainly notsomethingt h e y care a bout . 
[ citation neede d]

w hat is mis s ing?

~~ ~
pjm lp
So ma ny things . 
\- Swin g
\-Jav aFX \-  NIO and NIO2 \- i nv oke dyn ami c

\- m eth odhan dle s
Are a fe w that c om eto  m y m ind,b ut basic al lybe sid es fr o m what  wasleft  o ut ofJava 6l ib r a ries ,al most  ev er ythin g th a t w as intr oduced in  Ja v a 7an d8.

~~~ 
kllrnohj
Swi ng  & JavaFXar e n ot par t of the J CL. Those are addon lib r aries.
NI O: [h ttps ://develo per .andro id. c om/ref erence /java /n io/ p a ckage - su m.. .] (https://d e v elo per.a nd roid .com/re ference/java/nio/p a cka ge-summary.ht ml) 
"ad d e dinA PI 1"
A s  in , it's been there  since for ev e r.  What arey oure ferring  to spe cific a lly?

N IO2:
[htt ps://deve lo per. a n dro id.com/ref erence/j ava/nio/f i le/pa c ka g...] (ht tps:// de vel oper. androi d .co m/ref erence /j ava/ni o/fil e/ package- 
summary.html)

Invokedynami c: is  aruntime
 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
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.googlesource.com/platform/libcore/)

[https://android-
review.googlesource.com/#/q/status:open+open...](https://android-
review.googlesource.com/#/q/status:open+openjdk)

~~~
kllrnohj
> but_achieving feature parity is certainly not_something they care about.

[citation needed]

what is_missing?

~~~
pjmlp
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.

~~~
kllrnohj
Swing & JavaFX_are not part of the JCL._Those_are addon libraries.

NIO:_[https://developer.android.com/reference/java/nio/package-
sum...](https://developer.android.com/reference/java/nio/package-summary.html)
"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...](https://developer.android.com/reference/java/nio/file/package-
summary.html)

Invoke dynamic:_is_a runtime