The music thing is nice too, but it's either a paid solution or an incomplete one. Apple once released a stat that only 10% of the music on iPods comes from iTunes (most of the rest is either pirated or ripped CDs).
The music thing is nice too, but it's either a paid solution or an incomplete one. Apple once released a stat that only 10% of the music on iPods comes from iTunes (most of the rest is either pirated or ripped CDs).
I'm not saying any of this is bad; time machine is a lot easier to use for a non-techie than rsync is, just saying that taking an existing technology, putting a lowercase i in front of it, and selling it as a game-changer has been Apple's modus operandi for quite some time now.
Time Machine is a lot more than branded rsync. It's usable branded rsync. And the usability is what makes it a "game-changer" in the consumer market where rsync and its algorithmic innovation isn't.
In many ways, it's the same thing that canonical is doing with ubuntu, except they have sweet sweet luxury hardware money backing them up compared to canonical's comparatively meagre support contract money, or whatever else it is that they do for cash.
Oh and let us not forget: isn't it a key part of the point of OSS is that it's OK, nay even encouraged for people to "steal" the ideas? I thought the concept of stealing an idea, especially a software idea, was supposed to be meaningless? Should the Australian National University have patented rsync back in '96?
Honestly, if I developed rsync, the fact that Apple was using it to power Time Machine would be quite an acknowledgement to me.
Being able to tell people about your achievements is a lot better than having everyone pre-aware of them anyway IMO.
(Also it should be pointed out that time machine doesn't actually use rsync at all, or anything like it. It uses a totally different and much simpler system, seemingly built on their own FSEvents API and a load of hardlinks.)
2011-06-12 -> 2011-06-13
On my Linux machine when I do rsync backups it has to create a new inode for each file in the new directory whether or not it has changed. Even on a moderately sized directory tree this can take an hour or more (you can benchmark yourself with "cp -al". Try copying your whole disk just for fun). Time machine completes a cycle in 10 minutes or so and that includes the new data copying.For small amounts of files I agree with you that the hard linked directories would make a trivial difference. Keep in mind that by default Time Machine backs up /usr, /Applications and /System along with your user data which is quite a lot of files in the end.
That's all just creating the new backup's directory tree. The new data copying itself is fast because Time Machine uses the FSEvents API (which is like inotify but more suitable for backing up) so that it knows exactly what it has to back up beforehand (no scanning). If your computer crashes or you switch disks or otherwise screw up your FSEvents DB then it does have to scan the whole disk looking for changes and that can take hours.
So technically it is fast because it uses FSEvents and also because it can hard link directories. If either of those things are missing then the process would be significantly slower.
You are correct, for all definitions of "decentralized" that are "rigidly centralized, almost appearing decentralized because centralization is so far outside your control"
That's why I like the Apple vision - it leaves my data with me. It doesn't lock it up in a cloud somewhere.
In short: nothing to see here, please move along.