5 ms·
Rolling it out first on iOS at all doesn't seem like the right approach. If I were somehow in charge of it, I imagine I'd want to do it like: 1) ship it as off
by mikeash 10y ago
Rolling it out first on iOS at all doesn't seem like the right approach.
If I were somehow in charge of it, I imagine I'd want to do it like: 1) ship it as officially supported on the Mac, but off by default. 2) a year or two later, ship it as officially supported on the Mac, on by default, but still allow HFS+ as an option. 3) A year or two after that, if all has gone well, then introduce it into iOS (where presumably it's not reasonable to make it optional).
It's really weird to me that Apple is rolling it out to hundreds of millions of devices all at once, when it's not even a bootable filesystem on any of their platforms yet. Seems like the kind of thing where you'd want to take a more gradual approach.
I get that HFS+ is super old and I see why Apple wants to switch to APFS. But I don't get why they're in such a hurry.
Here's hoping their approach works well, in any case!
- MBCook 10y agoThe iOS filesystem environment is WAY more controlled than OS X. Updating OS X first would be fewer machines but is the much more difficult task. This would also be one hell of a production test. They obviously think they're ready.
- coldtea 10y ago>If I were somehow in charge of it, I imagine I'd want to do it like: 1) ship it as officially supported on the Mac, but off by default. 2) a year or two later, ship it as officially supported on the Mac, on by default, but still allow HFS+ as an option. 3) A year or two after that, if all has gone well, then introduce it into iOS (where presumably it's not reasonable to make it optional The plan doesn't make much sense. For one, the Mac has way more edge cases than iOS (in that people do more, and in more low- and -high level ways) with the filesystem, including running all kinds of unix userlands, exchanging files with other filesystems, etc. In iOS all fs APIs and access are tightly controlled, and there's no mounting of disks, no touching outside the sandbox, no disk management apps, etc. So iOS is a much better target for first launch than OS X. Second, with this plan it would take 3-5 years to ever arrive. Why so late? Apple has been developing it for a while, and probably have thousands of tests it has to pass. And they have been running it on 1 million or more devs on the 10.3 beta program on actual devices for feedback for 2 months.
- mikeash 10y ago3-5 years seems to be pretty typical for a filesystem to go from merely available to being battle tested enough to use without thinking about it. Bugs could destroy people's data (and the cloud won't necessarily help if the bugs corrupt data rather than erase it). What's the hurry?
- coldtea 10y ago>Bugs could destroy people's data (and the cloud won't necessarily help if the bugs corrupt data rather than erase it). There's no reason to expect bugs if you have a comprehensive test suite and extensive internal and beta testing (like with a million of registered iOS developers running it for months). Doubly so if you control most of the APIs and interactions with the OS tightly in your platform (as iOS does).
- mikeash 10y agoWhich is why the rest of iOS has no bugs? This statement makes me wonder, have you written any software before?
- coldtea 10y ago>Which is why the rest of iOS has no bugs? It has no show stopper bugs, and is used by close to a billion everyday just fine. And the "rest of the iOS" (kernel, userland, etc) is orders of magnitude more LOC than the filesystem. And with all kind of interactions between components, not just a constrained API that all sandboxed apps use, as is the case with an FS. It has way bigger test surface and (presumably) way smaller test suites than an FS would. What's the reason to assume an FS which is under production for 2 years now at least (it didn't appear magically formed a day before last WWDC) will have not just some obscure or infrequent bugs, but data killing bugs? (And why they'd be more than with the frequent new features and changes that Apple made/retrofitted to HFS over the years? Because they've started from scratch?)
- 10y ago
- 0x0 10y agoiOS has always used case-sensitive HFS, while macs usually need case-insensitive HFS. Since it looks like APFS will drop support for the case-insensitive file system mode, it makes sense to do the forced upgrade on the system that already uses a case-sensitive file system (= iOS). Plus, it's more straightforward recovering from a broken FS upgrade on iOS since many customers will have iCloud backups enabled, or at least their data stored on iCloud drive, while a mac filled to the brim with all sorts of strange applications and files spread all over the filesystem, likely never been backed up properly, is a tougher call.
- CameronBanga 10y agoI don't have a source, and too tired to look it up. But I thought I saw someone back away who found some tucked away support in APFS for case insensitive file support on macOS. Maybe misremembering. But someone had hacked it to run as a boot drive, and in doing so, found the setting.
- tehabe 10y agoThe problem with supporting APFS and HFS+ at the same time is that FileVault and Time Machine need to be very different on APFS. FileVault can take advantage of the transparent encryption feature of APFS and TimeMachine can simply backup a snapshot of the file system. I don't know if Apple (who likes to drop things) will support both concepts. Also the reason why I assume that APFS will be coming to macOS in the next major release and not in a point release.
- h1d 10y agoWhat do they care about macOS? I need to see desktops revealed soon.