What about ext4? Oh wait - no file data checksums - so a "no go".
Actually, it turns out plenty of folks have built plenty of storage on these platforms - including APFS.
In particular, for APFS, apple uses ECC for all hardware, uses fletcher checksums for metadata and I believe does a copy on write approach to help handle sudden power loss events etc. It seems to be working out OK for them given the prices they charge.
Also, we are left to wonder if their "reliable" SSDs are as reliable as checksums at the filesystem layer (or as reliable as both). I suspect the answer is yes, for the majority of applications running atop APFS (which is to say, iOS). Probably not for video assets on that Promise MPX bay (i.e. "external" non-Apple storage media).
Apple’s hardware choices are irrelevant.
If you're going to design one now, is there any reason to not have a checksuming capability? At least as an option, even though it may be default-off.
At least optional checksums should be supported, then watchOS does not waste time with it but a user with 10k+ mac workstation who might still uses spinning rust for bulk data storage is SOL.
That's.. an extremely confusing way to put it. ReFS and btrfs are from-scratch new FSes.
Is NTFS+ the default on Windows 10 / Windows Server 2016 or 2019?
APFS is shipping today in quantity / as default and I believe they back migrated literally millions of devices to it something like a year ago.
I don't understand the user use case with a 10K workstation and no raid (ie, with parity etc) + SSD with internal error correction. So this is a $10K workstation with magnetic disks and no other error correcting option / layer? Why do this?
Not to mention all the ..BSD or ZfsOnLinux based storage solutions.
I am not denying that APFS is a good FS, but not even having the option of checksums given its contemporaries was clearly a political and financial decision to benefit Apple and not its users. Pointing to an opaque mix of raid (and indeed, raid10 is not even enough), super-reliable SSDs and the full stack control doesn't make the lack of checksums any better.