4 ms·
On slide 52, which is supposed to demonstrate that the Android and Java source code implementations differ, it's clear that the Android definition did not come
by shadowmatter 14y ago
On slide 52, which is supposed to demonstrate that the Android and Java source code implementations differ, it's clear that the Android definition did not come from Android: The anotherString parameter is not referenced, and there are no offsets as parameters.
I also find it amusing that in Oracle's slides, "Java On Our Computers" is demonstrated with the Java update screen. Sigh.
- cpeterso 14y ago> I also find it amusing that in Oracle's slides, "Java On Our Computers" is demonstrated with the Java update screen. Sigh. Is the Java Updater even written in Java? That would be an even funnier example of "Java On Our Computers." :)
- TazeTSchnitzel 14y agoThe controls in it have a strange, non-native feel, so I'd hazard that it might be.
- lstoll 14y agoIt is however possibly the only obviously 'Java' experience that most non-techinal people have had. If you're trying to prove to them that Java is everywhere, this is what's going to make them think "Oh yeah, it's on my computer too"
- jimmyvanhalen 14y agohere are Oracle's slides. I hate to say, Oracle's evidence are much more convincing. http://www.oracle.com/us/corporate/features/opening-slides-1592541.pdf http://www.oracle.com/us/corporate/features/opening-slides-1...
- ghshephard 14y ago...Or they would be if they hadn't used a PDF generator that managed to completely befuddle Safari. I believe this is the first time I've ever seen a PDF that Safari can't render.
- stevewilhelm 14y agoIronically, it's quite legible in Chrome.