Aside from control, what does this provide over Linux?<p>IMO, the Linux desktop problem is due partially to relying on the antiquated X Windows system, but mostly a lack of funding a good vision, e.g. Unity.<p>After growing up with OpenLook, then Motif, the plethora of Linux window managers, and unhappy years with Windows, I noticed most of the elegant apps were being written for OSX. I’m not sure how much of this is due to the devs or the OS/libraries, but probably both.<p>The solution I want is a Linux OS, a WM with a good, cohesive, long term vision, and an easy way to build apps within at vision — something like a native Electron minus the memory and CPU overhead. I believe Google could do this.
The actual commit includes some details on disk paver.<p><a href="https://github.com/fuchsia-mirror/docs/commit/520ed01fd6f2585bd75607e3671604b5de7998fa" rel="nofollow">https://github.com/fuchsia-mirror/docs/commit/520ed01fd6f258...</a>
Linux is the last Unix and that is ok. Unix is a philosophy, not an implementation. Linux mocked Mach, but was usurped by the hypervisor, violently corralling Linux in a microkernel environment anyway. Lots of things are in the kernel that don't need to be, making them non-updatable, as someone else controls the keys. That past, present and future is awesome. But lets build from the past and build the future. Not saying Fuschia is it, but as Unikernels and Exokernels have shown us, Linux itself is just an app in the stack. Unix is a framework for running processes. Your domain problems are the real problems, the OS is an implementation detail.
From Wikipedia: <i>Chrome OS is an operating system designed by Google that is based on the Linux kernel and uses the Google Chrome web browser as its principal user interface.</i><p>OK so why not Google Chrome web browser on top of Fuchsia, instead of Linux kernel and the usual user space stuff? Google can call that retrofit anything they want, so it could still be Chrome OS.