3 ms·
And thus we returned to the stone ages of unjournaled FAT(-like) filesystems or bad NTFS driver implementations (the only good one is Microsoft's, and I doubt t
by lucb1e 12y ago
And thus we returned to the stone ages of unjournaled FAT(-like) filesystems or bad NTFS driver implementations (the only good one is Microsoft's, and I doubt they'll be handing over the code for Chromium).
It's not even something consumers see, it's a driver for crying out loud. It doesn't even make sense to remove it for "product simplicity" as they are claiming now.
Edit: Left a comment with another argument about FAT being a bitmap filesystem (versus ext4's binary trees) and that developers are the people that are going to code for their OS. Ignoring the 1% is not the smartest move. https://code.google.com/p/chromium/issues/detail?id=315401#c45 https://code.google.com/p/chromium/issues/detail?id=315401#c...
- wutbrodo 12y ago>It's not even something consumers see, it's a driver for crying out loud. It doesn't even make sense to remove it for "product simplicity" as they are claiming now. I may be confused, but isn't the discussion about removing support in the files app UI (while actual ext support remains in the console)? That would mean the exact opposite of what you're saying: it's a UI change, not a driver change.