Originally posted by gilboa
View Post
1. Most of the issues you describe are Google's own doing. They chose to let Android OEMs do what they want.
No reason to believe that they won't let Fuchsia OEM do the same.
2. Most of the closed-source blobs in any Android handset is actually Google's own code and its mostly user space. You can live with an old kernel. Far hardware (if not impossible) to live with old Google and unsupported Google apps.
The bulk of Android is actually abstracting the abstractions that abstract each stupid hardware-specific little shit way the hardware manufacturer decided to implement each feature. The media player subsystem is an example of this.
3. While theoretically a micro-kernel OS can recover from a crashed blob GPU driver, a buggy driver will be just as bad if its run in user space.
4. More-ever, you assume that you'll be able to take a GUI driver from Fuchsia 1.x and use it on a newly updates Fuchsia 2.x.
I fully expect Fuchsia blob drivers to last more than a couple months, it's not a tall order.
The whole reason they last a month on Linux is because Torvalds and others specifically decided to not have a stable binary interface, and this is good and fine for opensource drivers, but makes Linux the worst possible choice for blob drivers.
Thus far, beyond RHEL (and Windows servers) I've yet to see any OS, monolithic, hybrid or micro-kernel based, that actually live up to this promise.
Also note how projects starting now can learn from older projects and not make the same mistakes.
Comment