Yes, we'll see what WWDC has to say about APFS. I'd wager it'll turn out to be a lot more mature than you think. The "no frills" APFS released to developers in 2016 was, essentially, the APFS they needed for iOS. You might say they were using Macs to test the iOS release. The release that was rolled out without a hiccup a short while ago. Sure, it was "single device oriented." That was the scenario with the highest test priority.
There are several ways to read this statement made in the intro to
Apple File System Guide: It's now 2017, and Apple File System has been released as a bootable file system,
for iOS. It doesn't necessarily mean it will be released for MacOS in 2017.
That statement is not what I was talking about
THIS is what Apple said in later years WWDC session. Straight from the transcript.
" ...
So Apple File System will ship, by default on all devices in 2017. So to summarize, Apple File System will be the default file system for all Apple products 2017, it's ultra-modern, it's crash protected, it supports Space Sharing, we support cloning and snapshots. Enhanced data security features like the multikey encryption that we just discussed. ..."
https://developer.apple.com/videos/play/wwdc2016/701/
That was extremely aggressive. When got to this Spring 2017 and there still is no beta bootable macOS ... and gobs of missing macOS features and a likely October time frame ship date for next macOS . There are
major problems there. An "Oh, we think we finished the macOS version now ... you only have about two months to find the bug before we wrap for ship" That is more than radical when talking about a basic OS functionality and declaring ready for default when
The real question would be is whether Apple is going to start to throw features out the window to hit the deadline. Bootable is probably tractable in whatever limited context lines they want to draw.
How could they possibly throw a backup solution under the bus? "Sorry, if you upgrade to MacOS 10.13 you won't be able to make backups."
what part of the target disk doesn't not have to be APFS to work don't you get? The way time machine works now will
copy from APFS just was well as it does from HFS+. It would just he same mechanisms as it does right now. You target TM disk would be the exact same file system as it is right now. It is a corner case where TM devices is the same as device being used by user. It is another disk from where the OS lies.
I know folks look at APFS and think there will be a radical improvement in TM, but look close this really isn't a major TM improvement foundation. There are tons of missing pieces here. It is Apple's "ZFS like" solution.
How could they possibly throw multi-drive configurations under the bus, "Sorry, upgrading to MacOS 10.13 will break your Fusion drive." No way. These are capabilities that had to be addressed in fundamental file system architecture, and it seems clear, from my reading of Apple File System Guide, that those needs were anticipated.
"Default" doesn't mean mandatory. It would extremely straightforward for the new OS installer to look at the current volume and if Apple RAID or CoreStorage virtual volume to just skip the file system conversion. They are being thrown under the bus, but would be left in the status quo state.
For the new products there just wouldn't be Fusion Drive configurations.
Yes, Time Machine could continue to exist as an HFS+ volume, but the same efficiencies that an internal drive gains from APFS (cloning and deltas) are very attractive for the Time Machine scenario (deltas in particular).
Expect APFS has no mechanisms for transferring deltas from one volume to another. There is nothing like ZFS send/receive there. Getting to snapshots require mounting.
There is far more skewed toward making multiple OS/App volumes for testing in a software development context than that of backs. "Clone this OS drive image and they run the upgrade on it. Does it work? No throw away start over. ". As oppose browse this archive rapidly by time action you'd do in a time machine viewer.
The other natural fit is to Apple's "versioning" system they have for files. Again typically done on a single device/volume.
But Time Machine... I don't see it. Looking at the compression, but skipping delta transmission I think misses some significant issues. The intra-copies can be as much of an issue as a benefit across volumes (which again... that point of view APFS doesn't really comprehend). At least not with the interface they have now.
To me, safety features like copy-on-write and Atomic Safe-Save, and upping the maximum number of allocation blocks to 9 quintillion suggests that logical volume groups that bridge multiple external drives may be supported.
Eventually. The major dust up is Apple's spin that this is ready for default prime time in a several months with highly limited, narrow beta windows. There is a ton of "we have al lthe test cases we need in house" in their posturing...... we is extremely likely BS. Real users with diverse configurations almost always find new, often severe, bugs that lack of imagination and/or effort of the original software development lacked.
APFS has potential. It is just not likely ready for default for macOS anytime this year. If Apple is trying to do that I think they are trying to pound a round peg in a square hole. That was their openly stated position last year. If it is changed they should have said so clearly earlier than WWDC 2017.