Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!.POSTED!not-for-mail From: BGB Newsgroups: comp.lang.java.programmer Subject: Re: =?UTF-8?B?QW5kcm9pZOKAlFdoeSBEYWx2aWs/?= Date: Wed, 08 Jun 2011 12:08:00 -0700 Organization: albasani.net Lines: 53 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: news.albasani.net 7tzXDIYGzGcZMZyfYQ4QMYsXSUwFZ+mZao+/fzKErlpNRsuaQPD4G61tzLRMMPw1UAhYQgXRR6OoiiV7V8IlIA== NNTP-Posting-Date: Wed, 8 Jun 2011 19:11:17 +0000 (UTC) Injection-Info: news.albasani.net; logging-data="9lUQZosAgD+ulFdig6GoufSszoLHwIA707Bq13ApuTtTtIgV484VCI1KQON8HzqxGT02s370TFhOdFQ8ino8LSAq87q9razTY4370akhudViRegSBJfl6P1Vc2s/qbMn"; mail-complaints-to="abuse@albasani.net" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 In-Reply-To: Cancel-Lock: sha1:oh5/eKwLZWl7KJ/w7oyn/IgIPrE= Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:5132 On 6/8/2011 9:16 AM, Abu Yahya wrote: > On 6/6/2011 2:15 PM, BGB wrote: >> I was curious earlier, and downloaded the Android SDK, and made an >> inconvenient observation: >> the emulator is slow... >> >> emulating an older version of Android, it is ok, but trying to emulate a >> newer version, performance is unusably slow. >> >> >> maybe a similar issue might apply to iOS, meaning that maybe the >> emulated version is not an adequate representation of how it will behave >> on real HW... >> > > I must mention that it's not the case with the iOS simulator. I've been > using it for sometime now, and it always starts in a snap and responds > amazingly well. It's the envy of my colleagues who code for the Android > and Blackberry platforms using Eclipse, where the emulators take forever > to load. > maybe Apple knows more what they are doing?... I tried simulating Android 3.1, but the emulated OS was generally very unreponsive, like basically "click, hold, wait several seconds, something happens, ..." eventually got a lock image on the screen, and it would no longer do anything past this point... Android 2.x is a bit more responsive though, but still not really an example of raw speed either (turning off some graphical effects though, like menu-transition and scrolling effects, did make it a bit faster though). I also observed that they have a shell, but the shell sort of sucks (not nearly as good as Bash...). I am wondering it this is more a matter with fundamental limitations (say, Android takes too much processing power or requires simulating a GPU or similar), QEMU (not simulating ARM efficiently, ...), or with Google (say, they wrote inefficient HW emulation code, ...). in total, I am not terribly impressed either with the emulator or with the NDK tools (strange build setup, ...). since I don't have a smartphone either, there is not a whole lot of real reason for me to bother with all this. or such...