Article 6DGF8 ChromeOS is splitting the browser from the OS, getting more Linux-y

ChromeOS is splitting the browser from the OS, getting more Linux-y

by
Ron Amadeo
from Ars Technica - All content on (#6DGF8)
chromebook13_7-640x427.jpg

(credit: Valentina Palladino)

It looks like Google's long-running project to split up ChromeOS and its Chrome browser will be shipping out to the masses soon. Kevin Tofel's About Chromebooks has spotted flags that turn on the feature by default for ChromeOS 116 and up. 116 is currently in beta and should be live in the stable channel sometime this month.

The project is called "Lacros," which Google says stands for "LinuxAndChRomeOS." This will split ChromeOS's Linux OS from the Chrome browser, allowing Google to update each one independently. Google documentation on the project says, "On Chrome OS, the system UI (ash window manager, login screen, etc.) and the web browser are the same binary. Lacros separates this functionality into two binaries, henceforth known as ash-chrome (system UI) and lacros-chrome (web browser)." Part of the project involves sprucing up the ChromeOS OS, and Google's docs say, "Lacros can be imagined as 'Linux chrome with more Wayland support.'"

Previously ChromeOS was using a homemade graphics stack called "Freon," but now with Wayland, it'll be on the new and normal desktop Linux graphics stack. Google's 2016 move to Freon was at a time when it could have moved from X11 (the old, normal desktop Linux graphics stock) directly to Wayland, but it decided to take this custom detour instead. Google says this represents "more Wayland support" because Wayland was previously used for Android and Linux apps, but now it'll be used for the native Chrome OS graphics, too.

Read 3 remaining paragraphs | Comments

External Content
Source RSS or Atom Feed
Feed Location http://feeds.arstechnica.com/arstechnica/index
Feed Title Ars Technica - All content
Feed Link https://arstechnica.com/
Reply 0 comments