4 ms·
Not really, the thing is that implementations for accessing said file systems are under a GPL license. In order to integrate them to Windows, they'd have to re-
by Argote 14y ago
Not really, the thing is that implementations for accessing said file systems are under a GPL license. In order to integrate them to Windows, they'd have to re-implement from scratch which could lead to a ton of bugs and then they'd have to officially support all of those file systems.
Definitely not worth it from MSFTs perspective.
- shmerl 14y agoThey could implement it for the sake of interoperability. Surely it doesn't worth it from MS perspective since they didn't do it. But the reason is not because they don't have resources or it's some extremely hard problem to tackle. The reason is that they don't care about interoperability until forced. That's their whole approach.
- marshray 14y agoSeriously, how big of a use case do you think it is that someone has a drive formatted with some FreeBSD filesystem which they want use in Windows? How hard is it to just copy the data over a network or mount the image in a VM running its native OS? Note that support for the .iso filesystem was recently added.
- foxbunny 14y agoCopy 2TB JSF partition over network sounds like something I wouldn't want to do... An easier solution is to just get a Live Linux distro, and another 2TB NTFS partition, and copy over the data... if you have another 2TB drive.
- marshray 14y agoI know the world looks different when you're the server admin who has to deal with it, but how often does such a partition end up on a Windows server in the first place?