3 ms·
I'm a non-iCloud user (well, sort of), and I can't fathom a scenario where I would ever be tempted to use it. However, it's completely understandable what happe
by Udo 14y ago
I'm a non-iCloud user (well, sort of), and I can't fathom a scenario where I would ever be tempted to use it. However, it's completely understandable what happened here and the guy even states this repeatedly: it was entirely his fault. He corrupted his own data.
That said, the magnitude of problems resulting from this surprised me. What happens if an iCloud sync folders gets corrupted due to a technical problem one day? Isn't this fragility also kind of a nightmare for Apple's developers?
- gwillen 14y agoYeah, I don't think he can reasonably declare this to be his own fault. He's doing that to avoid criticism, but realistically, there's no conceivable reason that moving the local endpoint of the sync on one machine should cause the other machines to try to move their local endpoint. I can't even fathom how you could code it to make this kind of disaster happen.
- wvs 14y agoMost file references in Apple's frameworks track by both the target's path and inode, with the inode considered "more canonical". This is used in NSDocument apps where when you move a file with it still open, the app can tell where it went and continue working at the new path. Finder aliases (different from symlinks) also do this.