Is there a reason Apple does not allow for NTFS write support, even when Linux (free, open source) solutions can? Why don't they just utilize those existing solutions to support read and write for NTFS or other alternative file systems?
MacOS – Why doesn’t Apple ship and support FOSS drivers for NTFS write capabilities
filesystemmacosntfs
Related Question
- MacOS – the technical reason why OS X can’t write to NTFS devices
- MacOS – Cross-Platform File System file sharing between MAC, WINDOWS, LINUX
- MacOS – Paragon NTFS for Mac 14 doesn’t see NTFS disk (OS X 10.11 El Capitan)
- MacOS – How to completely remove Fuse for Mac OS X NTFS-3G
- MacOS – Disk encryption format for external drives that works on both macos and linux
Best Answer
I certainly don't speak for Apple, but to me a simple reason is that any code that Apple ships is installed across the globe and the code could have vulnerabilities, bugs or worse in it. Even perfect code has support costs associated with integration and end user support. Unless you want to pick a specific library, let's assume the popular OSS packages are no more or less buggy than OS X at this point to a first approximation.
There is a cost to even including the work even assuming no effort is made to test or support it. Apple provides free support to anyone at the genius bar, so there is a real business and opportunity cost for Apple shipping product that causes end users trouble. There also is a cost to train support personal to explain that OS X only ships with NTFS read support, but my estimate is that is trivial compared to what it would cost to even integrate the NTFS code let alone support it once it ships.
Apple doesn't go out of it's way to prevent users that want alternative filesystem code to run, but I can see many reasons why they don't incorporate even more open-source code then they do already on the ZFS/NTFS/extfs front.