I got a ChromeOS device a few years ago and it was great. I think they get an underserved bad reputation from being the locked-down devices you're forced to use in schools, but a personal ChromeOS device is a capable computer that can run any Android app or desktop Linux app.

Though having said that, in the past year I've replaced ChromeOS with desktop Linux (postmarketOS) and I love it even more now. 4GB of RAM was a bit slim for running everything in micro-VMs for "security," which is what ChromeOS does. I've had no trouble with battery life or Android emulation (Waydroid) since switching.

▲

pjmlp 7 hours ago | parent [-]

Not really any, Crostini has plenty of restrictions.

Cool if one wants to CLI stuff alongside Web and Android apps, but that is as far as it goes for GNU/Linux, with many yes but.

https://chromium.googlesource.com/chromiumos/docs/+/1792b43f...

▲

rossy 7 hours ago | parent [-]

Sorry, but "CLI stuff" is not "as far as it goes" with desktop Linux apps on ChromeOS. ChromeOS provides Wayland and PulseAudio servers to the apps as well so GUI and audio works too. It even synchronises file associations and installs a ChromeOS-like GTK theme into the container. The Linux GUI apps I had installed back when I used it felt completely native.

▲

pjmlp 7 hours ago | parent [-]

Without hardware acceleration and sound issues depending on the model, that is why I linked the page, as I was expecting such reply.

	▲	rossy 6 hours ago \| parent [-]
		It worked on my device. The page you linked looks very outdated and doesn't have my device's board or any device made in the past 5 years. The lists of unsupported devices also look pretty reasonable - old kernels, CPUs that don't support virtualisation and 32-bit ARM. Since modern ChromeOS uses the same virtualisation to run Android apps, I doubt there's a modern device where it doesn't work.