It may seem easier, but in the end a lot of work and conflicts may arise that make it more difficult or lead to negative results.

Remember, having the Android kernel on the phone and on the tablet made a big difference in the past where separate Android versions were needed. Now, there is a “general” PC that will also get the “Android” kernel. Due to the different types of hardware in a phone, tablet, and Chromebook, it becomes difficult to create a single core for them.

As far as I know, the ChromeOS kernel is based on GenToo. In my opinion, this means that potentially many different kernels will be baked based on the configuration in the gentoo build files. All simple and medium kernels for specific hardware combinations. Building one large kernel for this purpose (perhaps with enough diverse modules) is a challenge in itself.

I can imagine that the application interface provided by the kernel is different for the Android kernel than it is for GNU/Linux. ChromeOS has so far offered a GNU/Linux interface and the Android/Linux interface will be used. In particular, GNU/Linux-specific things that are not used in Android/Linux will also be removed from the ChromeOS kernel.

Ultimately, I hope ChromeOS continues to offer a Debian/Linux environment. But that shouldn’t be a problem, there’s another layer in between that can work things out.

[extra]: Now I think about it a little more: ChromeOS provides a Linux and Android operating environment. This modification will likely make the Android environment perform better, unfortunately perhaps at the expense of the Linux environment. This is explainable because Android apps are undoubtedly used more under ChromeOS.

[Reactie gewijzigd door beerse op 13 juni 2024 11:19]