> 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.
More interesting than I thought it would be. Hopefully this means better upstream GPU support for the plethora of ARM tablets/laptops that run ChromeOS.
That…feels very plausible? Microsoft has to be peeved at how much of the education market has been taken over by Chromebooks. Providing some locked down OS, with minimal specs, friendly to corporate management software, Teams preinstalled, etc feels like a pretty good move. The Chromebooks only work though an app store, so this idea could feed into Microsoft’s as well.
Unless Microsoft would rather target the cream of the market through their tablets.
Edit: then again, maybe they have become hooked on the Win11 telemetry + ad revenue. Stripped down OS has a harder time justifying the need to include Candy Crush.
Microsoft has had the sense to let Linux become the dominant OS on its cloud provider. Where it's the right tool for the job at hand, I suspect Nadella's Microsoft would be perfectly fine with being built on Linux.
I’ve recently used a Samsung galaxy book 5g that goes currently for $260 on Amazon running windows on arm64 and I feel this could be an indicator of how they easily could do this.
The really stunningly good ecosystem ripple effect of switching to Wayland is that anyone who wants to make hardware for Chromebooks now needs driver support for the one clear obvious huge target they should have had been targeting anyways, Wayland.
More directly obviously useful to most people though is just the fact that the shelf life of these units should hopefully be a lot longer. The OS might not longer get updates, but Chrome can keep upgrading & just run on whatever Wayland compositor is there.
Well, Wayland doesn't really depend on any drivers, but most Wayland compositors (as well as modern X11, as far as I know) depend on the Direct Rendering Manager/Infrastructure and related features. I suspect that Chrome OS already uses these, so there may not be a bit ecosystem difference from that side.
I'm hoping this means we will be able to run Linux binaries on ChromeOS at some point - I'm specifically interesting in being able to run Visual Studio Code (for Linux) and some dev environments and use Chromebooks plus a Linux-compatible OS as my dev machine.
ChromeOS seems to consider it an anti-goal for users to be using the OS like a general purpose OS. Crostini allows them to keep the rest of the system locked down, where-as just running vscode on ChromeOS directly would mean giving Vscode more unconstrained access.
You can already launch docker containers, lxc containers and windows, linux and even macos via KVM from crostini. You can even run nested virt inside those vms. Curious what the motivation is that those options do not address. Is it mainly resource allocation concerns?
I don't really understand the point of turning ChromeOS into Linux. The point of ChromeOS used to be a hardened secure browser only computer that would work identically with your login across systems on the platform. If you want a Linux laptop, why not just buy a Linux laptop. Why use do you want Google's dumbed down implementation of Linux.
One of the main points of the project was for security reasons.
Updates to the Chrome browser build for ChromeOS came out later than the standard Linux/Windows/Mac Chrome builds because the special chromeos build needed time to be integrated/tested with the rest of ChromeOS.
With LaCros, the browser can be updated independently from the rest of the OS.
They're not "turning ChromeOS into Linux." ChromeOS can and will still be a hardened secure browser-only computer that works identically with your login across systems on the platform. Having separate binaries for the UI shell and the Chrome browser doesn't nullify everything else. TFA even points out that users won't really notice any difference.
idk if you've used a chromeos device, but they have an infuriating update schedule where it seems like there are updates daily, and they _always_ require a full system reboot. they apparently can't be consolidated either, so half the time i'll reboot to apply one and immediately get a notification of another
this presumably allows them to ease that a bit and apply some updates with the system still running, with maybe a quicker browser-only restart
They will not convert whole system into native nabraries like gtk or qt. It is about dividing chrome binaries in order to get easier update process for developers.
[+] [-] smoldesu|2 years ago|reply
More interesting than I thought it would be. Hopefully this means better upstream GPU support for the plethora of ARM tablets/laptops that run ChromeOS.
[+] [-] nerdix|2 years ago|reply
This will certainly mean that Wayland will become a first class citizen and be less prone to random breakage.
[+] [-] 1MachineElf|2 years ago|reply
[+] [-] 0cf8612b2e1e|2 years ago|reply
Unless Microsoft would rather target the cream of the market through their tablets.
Edit: then again, maybe they have become hooked on the Win11 telemetry + ad revenue. Stripped down OS has a harder time justifying the need to include Candy Crush.
[+] [-] cykros|2 years ago|reply
[+] [-] zer0zzz|2 years ago|reply
[+] [-] happymellon|2 years ago|reply
That would be an interesting move.
[+] [-] TrueSlacker0|2 years ago|reply
[+] [-] verdverm|2 years ago|reply
[+] [-] jauntywundrkind|2 years ago|reply
More directly obviously useful to most people though is just the fact that the shelf life of these units should hopefully be a lot longer. The OS might not longer get updates, but Chrome can keep upgrading & just run on whatever Wayland compositor is there.
[+] [-] solarkraft|2 years ago|reply
[+] [-] sillywalk|2 years ago|reply
ChromeOS and Chrome browser can/will be updated separately, with Chrome being the same as the normal Linux version.
[+] [-] dmazzoni|2 years ago|reply
One hell of a long and expensive refactor.
[+] [-] samspenc|2 years ago|reply
[+] [-] Laremere|2 years ago|reply
[+] [-] sillywalk|2 years ago|reply
[+] [-] jauntywundrkind|2 years ago|reply
ChromeOS seems to consider it an anti-goal for users to be using the OS like a general purpose OS. Crostini allows them to keep the rest of the system locked down, where-as just running vscode on ChromeOS directly would mean giving Vscode more unconstrained access.
[+] [-] moondev|2 years ago|reply
[+] [-] femboy|2 years ago|reply
[+] [-] podgib|2 years ago|reply
[+] [-] 1MachineElf|2 years ago|reply
[+] [-] daft_pink|2 years ago|reply
[+] [-] sillywalk|2 years ago|reply
Updates to the Chrome browser build for ChromeOS came out later than the standard Linux/Windows/Mac Chrome builds because the special chromeos build needed time to be integrated/tested with the rest of ChromeOS.
With LaCros, the browser can be updated independently from the rest of the OS.
[+] [-] freedomben|2 years ago|reply
[+] [-] unknown|2 years ago|reply
[deleted]
[+] [-] fivre|2 years ago|reply
this presumably allows them to ease that a bit and apply some updates with the system still running, with maybe a quicker browser-only restart
[+] [-] pentagrama|2 years ago|reply
[+] [-] unixhero|2 years ago|reply
[+] [-] anonacct37|2 years ago|reply
[+] [-] deafpolygon|2 years ago|reply
[+] [-] NoZebra120vClip|2 years ago|reply
[+] [-] qbasic_forever|2 years ago|reply
[+] [-] nektro|2 years ago|reply
[+] [-] sillywalk|2 years ago|reply
[+] [-] helf|2 years ago|reply
[deleted]
[+] [-] TheDesolate0|2 years ago|reply
[deleted]
[+] [-] zer0zzz|2 years ago|reply
[+] [-] biblbroxxx|2 years ago|reply