No, why would the disable that especially on slow hard disks?
Exactly because of that. It would make them even slower.
Copy-on-write will fragment your data, which isn't at all as big of an issue on SSDs.
If we have a contiguous block of data, like this
A,B,C,D
and we then fill up some more data
A,B,C,D,1,2,3,4
And we then use the copy-on-write function to make a new reference to ABCD's inode
A,B,C,D,1,2,3,4,*
The * is the reference to ABCD. It doesn't take up any storage, simply refers back to ABCD. But now, if we make changes to our new copy, look what happen.
A,B,C,D,1,2,3,4,*,E,F,G
See the problem? To read the full ABCDEFG file, we first read from the start, and then we have to move the read-head past the 1234 block, to get the next portion of the file. Without copy-on-write, we would replace * with ABCD, and whilst it would take up more storage, we would be able to read the full, edited block contiguously.
[doublepost=1517571737][/doublepost]
Well, my iMac with a Fusion drive certainly still works. But HFS+ is embarrassingly old and lacking in some modern features that would make Macs better and more reliable. It was long past due we get a decent file system when APFS was released for iOS.
Old, yes - but what features is it you crave from APFS?
I'm not arguing against APFS. I agree it's good we're getting a modern file system. I just don't think we need to rush for it
