3 ms·
It's putting a positive spin on Xeno's Paradox. 100% minus 2% leaves 100% of the remainder! Until you remember that the quantum of a user-base is a user. I rea
by Intermernet 12y ago
It's putting a positive spin on Xeno's Paradox. 100% minus 2% leaves 100% of the remainder! Until you remember that the quantum of a user-base is a user.
I really don't know why they haven't adopted the (already existing) code from Android, or maybe even Gnome, KDE etc. that seems to solve the problem they purportedly face. If other projects (one of which is also a Google product) have solved this, why can't the ChromeOS team? I may be being naive, but why hasn't this issue arisen in other, similar projects?
I understand that they want to keep the codebase simple, but keeping HFS+ and VFAT while ditching ext* due to possible future security issues seems like a cop-out.