I can't compare it to other similar services, e.g. CrashPlan, because I haven't tried them, but I love it: fast, easy, fair price, works great on El Capitan, satisfying so far. Some things could be improved, though: I get it that system files and directories will not be backed up. But what about additions that the user has made to the system? Third-party extensions, homebrewed and other binaries in /usr/local/? It would be easy for the Backblaze servers to diff a client's system setup against the standard Apple OS X install and only backup the additional files & directories, those that are not OS X defaults. And /Library/Application\ Support/ does contain a lot of important things for the user, not only his home folder. (!) And why not your /Applications folder? As far as I can see, they don't give us a reason. Well, I have other local backup setups, so it doesn't really matter, if all that stuff isn't backed up to the Backblaze pods… well, except when there's a catastrophic event like a fire… and isn't that what Backblaze is supposed to be for? Getting *all* your important stuff back, when disaster strikes? Not the system, of course, but all the rest? Hmmm… Still, it's a great addition to cloning and Time Machine.