ChromeOS moves from a Gentoo-derived base that’s relatively close to desktop Linux to Android. Google wrote a technology that lets Linux X11 applications work with ChromeOS‘s display stack. Seems this is not a priority to be ported over.
Edit [2025-08-10]: I need to correct myself. According to https://www.androidauthority.com/android-16-linux-terminal-doom-3521804/ support for Wayland support is in development. I don’t know how much it matured in the months since that article. No idea if / how well it’s supported on X86, though, which is a requirement for Steam.
Why is it up to google?
ChromeOS moves from a Gentoo-derived base that’s relatively close to desktop Linux to Android. Google wrote a technology that lets Linux X11 applications work with ChromeOS‘s display stack. Seems this is not a priority to be ported over.
Edit [2025-08-10]: I need to correct myself. According to https://www.androidauthority.com/android-16-linux-terminal-doom-3521804/ support for Wayland support is in development. I don’t know how much it matured in the months since that article. No idea if / how well it’s supported on X86, though, which is a requirement for Steam.
It’s a pretty big change then… They should call it ChromeOS/2 or something.
Now you’ve got me wanting to try and run OS/2 Warp in a VM.
their loss
deleted by creator
Do you know if this means desktop Linux apps in general will no longer be supported?
Seems like Google moved to a new framework but X86 support may be a problem: https://www.androidauthority.com/android-16-linux-terminal-doom-3521804/
Maybe they no longer intend to keep some API/Protocol compatible.