Android Dalvik VM performance is a threat to the iPhone
Bryan Venable
Heath Borders
slow compared to compiled, languages.
I haven't implemented anything on Android yet, but most libraries that
will use CPU-intensive algorithms like those demonstrated by the
shootout are C libraries on the iPhone. For example, Quartz, the
drawing API is all C. While I agree that I'm less productive working
in C than in Java, I don't think speed is a valid concern on the
iPhone platform.
I've got user experience on an iPod Touch, a Palm Pre, and an HTC Hero
for the past 6 months. The iPod Touch has definitely been the
fastest. I'm really looking forward to getting iPhoneOS 4 on a new
iPod Touch (I'll probably buy a 4th-gen one) and Froyo on a new
Android device (I'm hoping to get an HTC Evo) and seeing how they
compare to each other. Unfortunately, the pre is not worthy of
comparison, despite having similar hardware to an iPhone 3GS.
-Heath Borders
hbor...@mail.win.org
Twitter: heathborders
http://heath-tech.blogspot.com
On Wed, May 26, 2010 at 4:04 PM, Bryan Venable <bven...@spif.com> wrote:
> http://www.javarants.com/2010/05/26/android-dalvik-vm-performance-is-a-threat-to-the-iphone/
>
Josh Jeffryes
experience is with the apps on each platform. Apple has a slim
advantage there, with it's emphasis on interface design in it's dev
docs, and it's insistence on Obj. C or HTML 5, but in the end that's
not really a compelling difference. Most users won't see Android apps
with bad interfaces, which makes it a non-factor (at least until the
first mass-adopted, badly written Android app gets out and crashes
everyone's phone).
What we really need to see to push the two apart is new developer
tools. The one that releases a completely kick-ass new dev tool first
will be the one that rockets forward. Think what Adobe was trying to
do with Flash CS5, but with native, non-crap code.
On May 26, 4:47 pm, Heath Borders <hbord...@mail.win.org> wrote:
> These articles are hilarious because of Java's early history of being
> slow compared to compiled, languages.
>
> I haven't implemented anything on Android yet, but most libraries that
> will use CPU-intensive algorithms like those demonstrated by the
> shootout are C libraries on the iPhone. For example, Quartz, the
> drawing API is all C. While I agree that I'm less productive working
> in C than in Java, I don't think speed is a valid concern on the
> iPhone platform.
>
> I've got user experience on an iPod Touch, a Palm Pre, and an HTC Hero
> for the past 6 months. The iPod Touch has definitely been the
> fastest. I'm really looking forward to getting iPhoneOS 4 on a new
> iPod Touch (I'll probably buy a 4th-gen one) and Froyo on a new
> Android device (I'm hoping to get an HTC Evo) and seeing how they
> compare to each other. Unfortunately, the pre is not worthy of
> comparison, despite having similar hardware to an iPhone 3GS.
>
> -Heath Borders
> hbord...@mail.win.org
> Twitter: heathbordershttp://heath-tech.blogspot.comOn Wed, May 26, 2010 at 4:04 PM, Bryan Venable <bvena...@spif.com> wrote:
> >http://www.javarants.com/2010/05/26/android-dalvik-vm-performance-is-...
Heath Borders
Android has a complete list of supported Java APIs. I would think it
would be an easier task.
-Heath Borders
hbor...@mail.win.org
Twitter: heathborders
http://heath-tech.blogspot.com
Justin Miller
> for the past 6 months. The iPod Touch has definitely been the
> fastest.
I'm not really surprised by this, as applications on the iPod
Touch/iPhone have thus far had pretty much free reign over memory, if
I recall correctly, as only one app is running at a time.
Eric Burke
--
Eric M. Burke
http://www.linkedin.com/in/ericburke
314-494-3185 (mobile)
636-294-0191 (home)
Justin Miller
Adam Horky
Hmmm... *cough* Windows *cough* ... :)
Josh Jeffryes
loss for the user? How does speed and battery life balance against
being able to run things in the background or switch between two
running apps?
Josh Jeffryes
I'd like to match and raise by the hundreds of hours I've lost to my
Adobe suite crashing.
On May 27, 2:27 pm, Adam Horky <adam.hork...@gmail.com> wrote: