Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!news.linkpendium.com!news.linkpendium.com!newsfeeds.ihug.co.nz!lust.ihug.co.nz!ihug.co.nz!not-for-mail From: Lawrence D'Oliveiro Newsgroups: comp.lang.java.programmer Subject: Re: =?UTF-8?B?QW5kcm9pZOKAlFdoeQ==?= Dalvik? Followup-To: comp.lang.java.programmer Date: Wed, 01 Jun 2011 08:02:23 +1200 Organization: Geek Central Lines: 21 Message-ID: References: NNTP-Posting-Host: 118-92-86-36.dsl.dyn.ihug.co.nz Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8Bit X-Trace: lust.ihug.co.nz 1306872143 19609 118.92.86.36 (31 May 2011 20:02:23 GMT) X-Complaints-To: abuse@ihug.co.nz NNTP-Posting-Date: Tue, 31 May 2011 20:02:23 +0000 (UTC) User-Agent: KNode/4.4.11 Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:4814 In message , Andreas Leitgeb wrote: > Lawrence D'Oliveiro wrote: > >> In message , Nasser M. Abbasi wrote: >>> The funny thing, is that Java when it came out, was supposed to >>> solve all these differences by putting a virtual OS between the >>> application and the OS, this way one writes to this one common >>> virtual OS (the VM) and not have to worry about the different >>> OS's below it. >> >> Those who knew the history of previous attempts to do this sort of thing >> could already predict why it wasn’t going to succeed. > > I wouldn't exactly call "one size fits *almost* all" a failure. It was never able to spread as widely as Sun originally hoped. And now we see attempts to fix up its flaws (like the substitution of Dalvik for the JVM in Android) raising the ire of Oracle, to the point where it wants to sabotage them.