Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!feeder.news-service.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Dirk Bruere at NeoPax Newsgroups: comp.lang.java.programmer Subject: Re: Why Do We Have ... Date: Sun, 03 Apr 2011 01:49:56 +0100 Organization: Dirk Bruere at Neopax Lines: 24 Message-ID: <8vpuh9Fo5fU1@mid.individual.net> References: <8uope3Ft9gU1@mid.individual.net> Reply-To: dirk.bruere@gmail.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Trace: individual.net 98LqvT4lho8n0KR14HPQagyD3RroA2mox+mf2TLKMNIeaZ7j68 Cancel-Lock: sha1:AjrJGoYCYb1O6hb+6bYA7mV1vAM= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 In-Reply-To: Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:2787 On 31/03/2011 13:18, Roedy Green wrote: > On Mon, 21 Mar 2011 11:00:19 +0000, Nigel Wade > wrote, quoted or indirectly quoted someone who said : > >> If you want to know why Android isn't Java you may be better asking Android. > > Android is a resource starved-environment compared with Java desktop. > Apps are small. You are constantly trying to shave bytes and CPU > cycles at the expense of program readability. You have roughly 200 ms > to respond or the user will perceive you as laggy. You have 5 seconds > to respond before the OS says your app has died. Your user is more > impatient and you have fewer resources to satisfy him. You are doing > everything you can to avoid draining the battery. This means letting > the screen go off, cpu turn off etc. whenever possible. That's got to change, at least with Honeycomb. I am working on a £200 ($300) Android 2.2 Tablet with a Tegra 2 chipset and half a gig or RAM. That kind of processing power was found on desktops not very long ago. -- Dirk http://www.neopax.com/technomage/ - My new book - Magick and Technology