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 491855
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[6]: People are disappointed
by kristoph on Tue 4th Oct 2011 23:47 UTC in reply to "RE[5]: People are disappointed"
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

dsmogor Member since:
2005-09-01

That's not so simple. Battery life is any decent in mobile devices only because the cpu is usually idle at 99.9% of time. That's why faster cpu's exhibit better battery life (which is counter-intuitive), because they expand the idle part.
That rule goes down to the os level, badly written apps can kill battery even running on the background by not letting the os put cpu in deep sleep state.
Besides that, the very process of going from idle to active is quite involving so the more frequently some process wakes up os to check something (eg. using polling instead of blocking) even if in effect it doesn't do anything the more the battery life is hurt.
Google has even implemented some hacks to Linux kernel (that were so bad that Linux community ultimately rejected them resulting in kernel fork) to make badly behaving apps have lesser impact of cpu wakeup frequency.

Reply Parent Score: 2