4 ms·
probably test their migrator for multiple months on hundreds or thousands of testing devices If I remember right, it was said at the time that they had include
by glhaynes 3y ago
probably test their migrator for multiple months on hundreds or thousands of testing devices
If I remember right, it was said at the time that they had included the migrator code in one or more of the releases before the one in which they actually did the migration. They ran it during those upgrades in a "do as much of the migration as we can without actually committing the changes" mode so that encountered errors could be reported back. So they had most of it tested on millions of devices.
- KRAKRISMOTT 3y agoThey ought to compensate users for the excessive flash memory writes if the users are going to be guinea pigs for their beta test.
- axoltl 3y agoThe writes would go to /dev/null. No "excessive flash memory writes" were done, as they were testing the ingest portion.
- orf 3y agoWhy?
- KRAKRISMOTT 3y agoBecause flash memory has a limited number of write cycles and an entire file system migration will gobble up a good chunk of it.
- orf 3y agoYes, but why should users be compensated for that. And why would it use a large portion of that, rather than an additional 1 write per cell?
- KRAKRISMOTT 3y agoBecause if you see OP's comment, they were testing their migrator on real users' devices (in what I presume is a blue green manner, without explicitly informing them except in small print) before their "official launch". If their beta test didn't go well, they will have to rollback their change, consuming more writes. https://news.ycombinator.com/item?id=40044310 https://news.ycombinator.com/item?id=40044310
- glhaynes 3y agoYou didn't get your check for 3 billionths of a penny when they were sending them out?
- mise_en_place 3y agoIn addition, there is quite a bit of dogfooding that goes on at Apple.
- JoshGlazebrook 3y agoI've read about those people who join a company just to fix a bug and its so tempting lol. I've been dealing with this bug for months now: https://www.reddit.com/r/MacOS/comments/17p415c/macos_sonoma_mouse_hover_bug_most_annoying_update/ https://www.reddit.com/r/MacOS/comments/17p415c/macos_sonoma... Hover just stops working on all windows unless you right click on another window, or hide windows to view desktop and come back.
- wdb 3y agoI have a similar problem where the rollover region is not at the actual position of the rendered element but much higher. So you where you have to hover over is above the actual element. Really annoying. Happens a lot on Twitter or Youtube website but also at other places.
- misternugget 3y agoThat's right, someone linked me to this article: https://www.macobserver.com/analysis/apple-dry-run-apfs-prior-ios-10-3/ https://www.macobserver.com/analysis/apple-dry-run-apfs-prio... Pretty impressive.