4,070 karma · joined August 8, 2010
[ my public key: https://keybase.io/maakuth; my proof: https://keybase.io/maakuth/sigs/PUeDomfzqvw6Kl00up-5Lb3EZsY7qhl7c78cGkw1w1w ]
Obviously it was going to be very difficult to compete as a third platform with the behemoths iOS and Android become during those years. At least the MeeGo and Windows Phone cards were not the winning ones.
Compare this to the deduplication approach: the filesystem would need to keep tabs on the data that's already on disk, identify the case where the same data is being written and then make that a reference to the existing data instead. Very inefficient if on application level you already know that it is just a copy being made.
In both of these cases, you could say that the data ends up being deduplicated. But the second approach is what the deduplication feature does. The first one is "just" copy-on-write.
ZFS deduplication instead tries to find existing copies of data that is being written to the volume. For some use cases it could make a lot of sense (container image storage maybe?), but it's very inefficient if you already know some datasets to be clones of the others, at least initially.
Here's a fun clip about it, focusing on British place names: https://www.youtube.com/watch?v=uYNzqgU7na4
I suppose the real economics are going to be better, as you probably need to make gas more expensive by carbon trade or something in order to decarbonise. And electrical power should be very cheap.