Hacker News new | ask | show | jobs
by EpicEng 1868 days ago
If your update system requires 1-2 days of "post-upgrade homeswork" time and slows your phone by 50% in the process, you've designed a very poor update system.
2 comments

It's a non-concern for 99% of users. iOS vs Android version piecharts always look like this:

https://www.alistdaily.com/wp-content/uploads/assets/alist-a...

Apple successfully upgrades a huge majority of all their phones in the field, and nearly all of those users are barely even aware of it. They plug their phone in at night, sometimes in the morning there's a message about a new version. Maybe they notice their phone is slow for a day or two, likely they don't. No major incidents involving mass-bricking of phones, no rollbacks, no data loss... arguably the most successful update system in the history of technology.

Why? Seems like this just ignores reality.

It’s just true that data structures change over time, and sometimes new features mean that old data needs to be re-processed.

> It’s just true that data structures change over time

Sure, but it seems only 1 of the OS's takes this long to be fully usable post-update. Why is that? Does Android not ever have to change data structures and if so, why doesn't it take their OS 24-48 hours of post-processing to finish the update? You find this acceptable?

Android doesn’t have the same feature set. Comparing the two like this is an obvious fallacy. For example, Apple does their ML e.g. for photos on device for privacy reasons, whereas Google does it in the cloud.

I’m not saying ML is the cause although it could be. I’m saying they are different products with different values, so expecting them to behave the same doesn’t make sense.

And yes, some background processing after an update is more than acceptable. It’s desirable if it means sending less data to Google.