Most Powerful Open Source ERP

NayuOS's future after Google

Little by little, Google is extending ChromeOS while leaving ChromiumOS in a kind of incomplete state. What will be the future of NayuOS in this context?

Last Update:2018-05-05

Version:002

Language:en

Page Content

Little by little, Google is extending ChromeOS while leaving ChromiumOS in a kind of incomplete state. The increasing gap between ChromeOS and ChromiumOS reminds me the now huge gap between Android and the Android Open Source Project (AOSP). Recent version of ChromiumOS on recent hardware are barely usable:

It seems that Google has decided to move key features of ChromeOS into the proprietary user space and to stop fixing essential features of ChromiumOS.

Should we keep on basing NayuOS on ChromiumOS? What are the possible ways out?

The ChromiumOS way

We would have to fix all bugs introduced in new versions: sound, bogus suspend, broken support of Asian languages. It is not that easy, especially for Asian language support, because the process of building and testing ChromiumOS is quite long. Also, certain features are directly implemented as Chromium browser extensions, something that can be difficult to add to ChromiumOS guest mode and for which little or no documentation exists.

Support of Android applications would be possible using Anbox, with enough effort.

In short: possible but effort is difficult to guess, from a few man week to a few man month.

The GalliumOS way

GalliumOS provides an alternative to ChromiumOS based on Ubuntu. It fixes most of the issues of ChromiumOS:

It even provides a simpler way to install Anbox than ChromiumOS would.

The only issues it has is that it is not based on the stable read-only, signed, trusted approach of ChromeOS for booting the system image. And it creates an incentive for users to install too many applications.

The Elbe way

Elbe provides a tool to build system images from Debian packages. It could be extended to support Linuxboot as firmware and provide something similar to the stable read-only, signed, trusted approach of ChromeOS for booting the system image. Elbe could be a way to build a browser-only GalliumOS image with Anbox.

The AOSP way

There are a number of non-free projects that turn Android or AOSP into a usable desktop system, including the default system provided on recent Huawei and Samsung phones. Independent solutions include:

Combining the two could lead to an alternative approach that could bring the advantage of unifying OS on all desktop and mobile, whereas Elbe approach unifies the OS on server and desktop. Maru seems to combine all approaches in a single solution, just like running Termux with proot on any Android device (but not reliably).

Conclusion

Unless Google decides to maintain ChromiumOS in a usable state, NayuOS will have to depart from ChromiumOS base.

I am interested to find out how easy it would be to derive from GalliumOS (with Elbe?) a read-only system image for Chromebooks that supports only three applications: a web browser. a terminal and a file browser. It would also be interesting how suitable could be a web browser such as Falkon on a Qt based minimal desktop such as LxQt. Could we reproduce something close or better than the ChromeOS experience?

The AOSP way is interesting but would probably require huge resources and would provide little compared to existing solutions on existing device. It is better to simply follow what Miraxess and Eelo are doing and rely on them.