Re: "Fragmentation is a myth"
No, it's not, but it depends entirely on the amount of flash memory and the flash controller in the device (and the version of Android). And 'memory fragmentation' is a bit of a misnomer, because it's really a result of flash controllers only being able to mark a 256K (typical) block of memory as available for re-use once all of the 4K (typical) pages have been removed. Eventually all of the blocks are in use, even though there may be a lot of free space as far as the filesystem is concerned. This leads to a lot of on-the-fly housekeeping to make space available again. Google TRIM or fstrim if you want to find out more about the problem.
For a device with small (4GB or less) of built-in flash, the time it takes to get to the point where it slows to a crawl because of this 'memory fragmentation' can be as little as a week or so (depending on what the device is being used for). Devices with more memory take much longer, and some devices may not show it until they are a year or more old.
Unfortunately, the way I read this is that all of my current android devices (including a phone that is still in warranty but unlikely to be updated because the ISP will not re-package the manufacturers more recent releases) will become unable to connect to the Play store when they bring this in. Most builders of these devices lose interest in packaging new releases of Android once they stop selling the device. This includes big names like Samsung, LG, HTC and even Google themselves, once they deem a device too old to take a new release.
This means that my perfectly usable 9.7" tablet running 4.0.4 is extremely likely to become less usable. Looks like I will have to play around with CyanogenMod after all.