Hacker News Reader

Disclaimer: I used to work at Google exactly on this project.

I'm so happy this finally made it to daylight! =) I was the original one researching for the feasibility of this, but at the time (3.5 years ago), the re-compression burden made it a no-go even for the most modern phones so we decided to table it.

View on HN

Possibly dumb question: why doesn't the hash verification take place on the uncompressed contents, moving recompression from the updating-critical-path to the nice-to-have-later-to-save-disk-space category?

My dream updater would just be a bunch of stream processors, so the downloading / decompression / disassembly (a la courgette), patching / recompression happens all at once, as the data packets come in (thus utilizing both CPU and IO). If done right an update shouldn't take much longer to complete than the download step, no?

Many (most?) Android phones are chronically short of flash space, even in the status quo storage shortage often prevents applying app updates. There is really no room to make storage use more lax.

Reply on news.ycombinator.com