But then you need a fat binary for your little installation program.
The installation program could be written as a cross-platform script interpreted by a native program. Better to maintain one cross-platform program if it means you don't have to for the others.
Of course, even if it gets that bad, I suspect it'd be defeated with something like duct tape.
Or putting it inside an A/V cabinet.
Taking from your list of actions: Pick a random block:
1. GC comes along, swoops up block, eliminates junk by flashing entire block into 1's (awhile later)
2. OS requires write, swoops up block, writes only the 0's from the file leaving everything else untouched.
In this manner each step does half of the writing amounting to one write when combined. This is exactly how all SSDs work. The major difference announced in the article is that they are separating the two steps.
Normally this is impossible because the SSD doesn't know if something can be cleared until the OS is trying to overwrite it. This makes writes take longer. The new firmware hopes to make writes faster by moving the first step into the idle time of the drive (by figuring out when a overwritten block is unused) sort of like how you can set up a download to only run when your not using the internet connection. It allows for more efficient use of time that the drive would otherwise be doing nothing with.
to disable "'non-essential hardware components' and applications on the phone, reduce power to the screen and potentially reduce the phone's processor speed. It also would make it harder to disconnect the call and enable 'emergency phrase buttons' on the phone."
Sounds non obvious enough to me.
Only on Slashdot would this be modded +5 Insightful.
Only on Slashdot would this be modded +3 Informative.