[sern]

I should have qualified my statement by mentioning that the Chrome app process runs a couple of background services - this causes it to be killed for low memory after normal background processes (the actual behaviour is a little more complex than that, but that's the gist of it), which could potentially impact the performance of multitasking. The proper thing to do is to run background services in a separate process from the UI or whatever uses the most memory so that the latter can be evicted more quickly.

I stand by my assertion that optimising for memory isn't a priority at Google. An Android engineer poignantly put it (sorry, can't remember who) when they bragged on G+ that Android 4.0.3 was the first time since Gingerbread that they'd run the OS on a <1G RAM device (namely Nexus S). Then again, as an actual embedded engineer (none of this gigs of RAM crap!), all I care about is memory usage...

[sern]

The comment I was referring to is under this G+ post: https://plus.google.com/105051985738280261832/posts/intiB73F...

[fpgeek]

Given the context and the joking tone (complete with smiley), I think you're reading way too much into the comment. Given the devices ICS had been shipped on at the time, she could have just as easily said it was the first time in a year that they'd shipped Android on:

- a single-core device

- a device with a screen smaller than 4.5"

- a device with less than 720p resolution

- ...