The project is called “Lacros” which Google says stands for “Linux And ChRome OS.” This will split ChromeOS’s Linux OS from the Chrome browser, allowing Google to update each one independently.
Previously ChromeOS was using a homemade graphics stack called “Freon,” but now with Wayland, it’ll be on the new and normal desktop Linux graphic 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.
I’m surprised Google has not retired Chrome OS yet. Feels like they’ve kind of lost their focus, so it’s about time to put it on the chopping block for retirement announcement
Speaking of which whatever happened to FuchsiaOS? Did they kill it? It would be a shame if they did. I was interested in it because it was an open source OS that wasn’t Linux or bsd based.
Never heard of it, “micro-kernel like” is a interesting phrase.
https://fuchsia.dev/fuchsia-src/get-started/learn/intro/zircon
seems to be still actively developed: https://fuchsia.googlesource.com/fuchsia/+log
ChromeOS is insanely successful though? In Europe it’s one of the most popular systems for student laptops and cheap hardware. It’s sold as a standalone option (x86 and ARM) in technology stores all over the UK.
Of course Windows still reigns supreme but even a fraction of that is a commercial success to a competitor like Google. Much like how Bing is a “failure” but handles a third of search engine traffic in some places; Which is colossal considering it was technically inferior to Google until the AI features brought it some rep recently.
Not that I like ChromeOS but it’s a lot more successful and commercially viable than a lot of the projects that they’ve shelved in the last few years.
