Between the Material You design and move to break apart the Chrome browser from ChromeOS, now more than ever, ChromeOS is Linux with Google's desktop environment.
The bit about modifying the Linux code is to say you can’t run a a built-from-source version of the kernel or DE, like you could do with Fedora or Ubuntu or Arch or distro.
The bit about “now more than ever” is because by separating the browser and OS (Lacros) it’s no longer the browser-based OS we’ve always known it to be. Now it’s Google Linux with Chrome browser (Linux And Chrome OS).
you can’t run a a built-from-source version of the kernel or DE
That’s sad, do you know why that is? Is it that you can’t use a generic Linux kernel as a drop-in replacement or that you couldn’t even modify the source of the kernel used by ChromiumOS?
And with “Google Linux”, do you mean its architecture is fundamentally different from the average distribution to be compatible with software that would otherwise run on it?
Well, you can build and run from source using Chromium. But that doesn’t have all the features of ChromeOS, just like AOSP vs what you get on a Pixel phone.
I can’t imagine that Google have changed the kernel architecture. I just meant to differentiate that it’s their own distribution rather than another Debian derivative or something.
Ah, you’re right, the fact that Chrome has stuff not on Chromium is a pretty big deal, a few years ago I tried to use a project that attempted to somehow bridge the gap, I think it was Brunch and it was a pain to get working.
it’s their own distribution rather than another Debian derivative or something.
Not easily, the accessible linux environment is a container that doesn’t give you lower level access. You can do more in developer mode I think.
Traditionally it has been an extremely minimal Linux distro with pretty much everything running in the Chrome process, if you ever looked at the processes that was nearly the only one other than system things. They are trying to separate the base “Linux distro” and the browser more to make it easier to maintain, so the browser will be a normal application.
The bit about modifying the Linux code is to say you can’t run a a built-from-source version of the kernel or DE, like you could do with Fedora or Ubuntu or Arch or distro.
The bit about “now more than ever” is because by separating the browser and OS (Lacros) it’s no longer the browser-based OS we’ve always known it to be. Now it’s Google Linux with Chrome browser (Linux And Chrome OS).
That’s sad, do you know why that is? Is it that you can’t use a generic Linux kernel as a drop-in replacement or that you couldn’t even modify the source of the kernel used by ChromiumOS?
And with “Google Linux”, do you mean its architecture is fundamentally different from the average distribution to be compatible with software that would otherwise run on it?
Well, you can build and run from source using Chromium. But that doesn’t have all the features of ChromeOS, just like AOSP vs what you get on a Pixel phone.
I can’t imagine that Google have changed the kernel architecture. I just meant to differentiate that it’s their own distribution rather than another Debian derivative or something.
Ah, you’re right, the fact that Chrome has stuff not on Chromium is a pretty big deal, a few years ago I tried to use a project that attempted to somehow bridge the gap, I think it was Brunch and it was a pain to get working.
I understand
Not easily, the accessible linux environment is a container that doesn’t give you lower level access. You can do more in developer mode I think.
Traditionally it has been an extremely minimal Linux distro with pretty much everything running in the Chrome process, if you ever looked at the processes that was nearly the only one other than system things. They are trying to separate the base “Linux distro” and the browser more to make it easier to maintain, so the browser will be a normal application.