41–50 of 60 posts
Earlier quoted context omitted.
Every time there’s an iOS update, the internet goes crazy about their phone being slow or hot or not holding a charge. Then, a day or two later, the background system processes finish doing their post-upgrade homework and everything goes back to normal.
Well I've been developing iOS apps for a long time, and updated many times. I don't remember anything as dramatic as this!
In case anyone missed it, the author of the submission added an update [1] saying that after some time the issue went away: > Aaaand it's fixed... I didn't do anything specific. It took a few hours (?!) after the upgrade. It scored many times low, but now it seems to score at a normal level (3000+). Really wonder what the explanation for all of that is. [1]: https://news.ycombinator.com/item?id=27131683 .
Not sure if it’s related at all, but it’s still sad to see that our devices have become so dependent on phoning home that they can become unusable when the home is not picking up or answering incorrectly.
In case anyone missed it, the author of the submission added an update [1] saying that after some time the issue went away: > Aaaand it's fixed... I didn't do anything specific. It took a few hours (?!) after the upgrade. It scored many times low, but now it seems to score at a normal level (3000+). Really wonder what the explanation for all of that is. [1]: https://news.ycombinator.com/item?id=27131683 .
Does iOS do the same post-install spotlight indexing as macOS? That’s often the culprit for post-upgrade slowdowns on Macs.
Speaking of slowness - not sure if i'm the only one, however Spotlight-searches on my iPhone (8 plus) have become dog-slow since sometime iOS 12 or so - before, the results would be instant - now it takes something between 3 and 5 seconds to return a list of Apps for example :(
Earlier quoted context omitted.
Well I've been developing iOS apps for a long time, and updated many times. I don't remember anything as dramatic as this!
Except for when apple started throttling phones with batteries below 85% capacity.
Earlier quoted context omitted.
Indexing or rebuilding I guess.
Yet no notification. The goblins inside the ios doing their thing behind closed doors. Even a heads-up saying "hey we're doing some work behind the scenes on your device as part of the upgrade" would do.
I could see a new something in the Settings that indicates post-OS upgrade showing migration status being useful.
Earlier quoted context omitted.
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.
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.
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?
Earlier quoted context omitted.
Every time there’s an iOS update, the internet goes crazy about their phone being slow or hot or not holding a charge. Then, a day or two later, the background system processes finish doing their post-upgrade homework and everything goes back to normal.
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.
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.
Earlier quoted context omitted.
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?
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.
Earlier quoted context omitted.
True, but it could be marketed a bit better: "Update finishing in the background"
This is how Android shows it, and I think it is quite good because the phone feels slower while finishing the upgrade.
