3 ms·
I'm not opposed to pointing fingers at Apple when it's justified, but I believe in this case it's really just a matter of priorities. My guess is that the numb
by lxgr 3y ago
I'm not opposed to pointing fingers at Apple when it's justified, but I believe in this case it's really just a matter of priorities.
My guess is that the number of users that use remote file storage providers is just much larger than that of users using actual (non-SMB) network or local (non-(ex)FAT) file systems, so they created a kext replacement for that use case first.
If anything, the File Provider API levels the playing field between iCloud and third-party remote storage providers, since the neat APFS tricks they can use to implement it would otherwise be unavailable to third party developers. For example, I find Google Drive to be much more well-behaved on File Provider than it ever was when using FUSE (I blame it for some hangs or kernel panics) or SMB (which was more stable, but did not support Spotlight at all).
For all the other use cases, I'm hopeful that we'll be seeing a real macOS FUSE sooner rather than later.