Linked by Thom Holwerda on Tue 4th Oct 2011 19:03 UTC
Apple I'm down with the flu at the moment, so I wasn't really looking forward to doing a detailed write-up of all the awesome stuff Apple was going to show off today. So, Tim Cook, thanks for talking about nothing for almost two hours straight. The only mildly interesting thing is a slightly specbumped iPhone 4, dubbed the iPhone 4S, which has a faster processor and graphics chip, better camera, and a few other improvements here and there to bring it in line with Android phones launched earlier this year. Sadly, Apple insists on the teeny tiny 3.5" screen, which is too small even for my girly fingers (I'm not kidding, I have to buy gloves in women's clothing stores). For the rest, it was a long rundown of iOS5 features we already knew, and improvements to voice recognition - which is something WP7, Android, and every other self-respecting mobile operating system does already anyway. They do claim it will sport a more natural feel to it, but only time will tell how well it'll work outside of pre-recorded and widely tested on-stage demos.
Thread beginning with comment 491851
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: People are disappointed
by Beta on Tue 4th Oct 2011 23:12 UTC in reply to "RE[4]: People are disappointed"
Beta
Member since:
2005-07-06

That Galaxy S2 your buying has a dual core 1ghz chip and that's the Samsung flagship so you think that's outdated too or is just about the screen ;-)


I think the S2 is outdated, its been kicking around for more than half a year now. There’s a new Nexus coming, and well, it sounds like it’ll have a 720p screen. yummy.

That's why Android devices pack more RAM in there; they need it.

Because they have true multi‐tasking, you’re right!

Reply Parent Score: 3

kristoph Member since:
2006-01-01

Because they have true multi‐tasking, you’re right!


Actually it's just because memory management in Android is poor in various frameworks, especially in the imaging stuff. But as I said this should be fixed in 3.1.

'True multitasking' in Android is not really practical. If you do anything in the background that is CPU intensive or network intensive it kills the battery so you can only do very specific stuff which you can do in iOS.

I appreciate it's a philosophical thing. Apple does not let developers do it because they don't want a poor experience for a user. Google is all about doing whatever the heck you want and if people get a bad experience then it's their fault for installing bad stuff. Both points have their merits.

Reply Parent Score: 2

JAlexoid Member since:
2009-05-19

Actually it's just because memory management in Android is poor in various frameworks, especially in the imaging stuff. But as I said this should be fixed in 3.1.


It's not poor, it's horrible. And 3.1 does not fix it, it only bumps the heap size of the app for tablets so the problem "magically" disappears.

Reply Parent Score: 2

juzzlin Member since:
2011-05-06

'True multitasking' in Android is not really practical. If you do anything in the background that is CPU intensive or network intensive it kills the battery so you can only do very specific stuff which you can do in iOS.


I have never understood how exactly multitasking kills your battery. Running tasks A and B simultaneously consumes just as much energy and clock cycles as running first A and then B. Or am I totally wrong?

Edited 2011-10-05 12:44 UTC

Reply Parent Score: 2