The Neo is the closest and the good thing is it has an actual OS to install apps onto. I'm not sure if via the Linux containers Firefox can be installed on ChromeOS.
...basically, I have "nerd cred" and run linux on my desktop, but for my laptop I wanted: disposable (no leaky hard drive), zero maintenance (no kernel modules for sound drivers), battery-portable.
90% of the time I'm wanting `vim` + `git` + `ssh`, and 20% of the time i'm wanting to run some random stuff locally. Chromebook is basically zero friction and 1/10th the price (and 1/10th the capabilities) of a "very nice mac laptop", plus you can pop into a very capable linux VM (w/ passthrough GUI support) without a lot of ceremony.
Windows laptops are out of the question, and pure linux laptops (until only very recently) were of marginal support and low battery capabilities (especially "close it and stuff it in a backpack for 3 days").
> Windows laptops are out of the question, and pure linux laptops (until only very recently) were of marginal support and low battery capabilities (especially "close it and stuff it in a backpack for 3 days").
Dell has sold laptops with first-party Linux support for nearly fifteen years, to say nothing of other smaller OEMS.
As for the battery issues during sleep: that actually has to do with a combination of the BIOS settings + downstream ramifications of secure boot (and how the old-fashioned "hibernate" used to work). Unfortunately, that isn't specific to Linux. My MBP has the same problem, and so do the same laptops running Windows.
"""last week: Pop!_OS 22.04: kernel 6.17.9-76061709 — module BTF validation cascade boots system to emergency mode #3961
Thanks for taking a look,
Quick update — I'd already recovered before seeing this comment. The path that worked: boot Pop_OS-oldkern, run sudo apt install --reinstall linux-image-6.17.9-76061709-generic linux-modules-6.17.9-76061709-generic && sudo kernelstub, reboot. 6.17.9 came up clean. The reinstall's postinst hooks ran update-initramfs automatically; /boot/initrd.img-6.17.{4,9}-* are both freshly dated 2026-05-06 (~11:44 / 11:46), and kernelstub copied them to the EFI partition. Verified: journalctl -k -b 0 | grep -iE 'btf|failed to validate' | wc -l → 0.
"""
In the year 2026, on my Linux laptop (T14, Linux 6.18.26) I ran the following:
lsmod | cut -f 1 -d ' ' | grep snd | wc -l
And it responded: 53. Fifty three kernel modules are dedicated to sound. I, of course, never had to install any of them by hand, or take any other direct care.
Those modules are all in tree. The distro chose to build them as modules. You could have built them into the kernel. I don't think that counts. When I hear about manually futzing with "kernel modules for sound card" I think you're running out of tree modules in 1997.
Chromebooks make a pretty nice, Linux friendly machine. They're usually cost optimized given the market they address, but that's fine if it fits your needs. Sometimes they have "weird" hardware, keyboard/mouse controllers and stuff at least wasn't always "pc standard", audio controllers seem to be commonly outside mainstream as well.
It's nice to run Linux on a machine that was built to run Linux. No silly windows key, no fighting with firmware that was built for windows first. I have a Chromebox that was a great mini desktop and the pricing was nice. My first Chromebook ran FreeBSD pretty well once it was no longer needed for ChromeOS, etc.
You have to shop carefully, you want something that's easy to put a MrChromebox firmware on and doesn't have any known issues with the OS you want to run. It's been a while since I purchased a ChromeOS device and the current state is different than it was then; I'm not sure how easy it is to find reasonable options now, but there were plenty of good options in the past. You also want to be sure that it has enough ram and storage for you needs or that those are expandable, but I think soldering ram and storage is pretty common across the range.
The number of people who have "installed linux" other than ChromeOS on a Chromebook is probably in the low single digits, while the ChromeOS installed user base is in the hundreds of millions. For any given thing someone is going to try to put linux on that thing, but it is not a common use case for Chromebooks that we need to discuss.
I was genuinely asking. In “my circles” a Chromebook is a cheap laptop that one can install Linux on. As in, “oh, I just picked up this used Lenovo Chromebook and installed Ubuntu on it”.
You'll get a more informative answer from them. I couldn't speak to their motivations. But I certainly wouldn't advise doing it. ChromeOS has better security and performance than Ubuntu, and it automatically updates things like peripheral firmware that Ubuntu isn't even aware of.
It feels like the wrong tool for the job in both directions. If you wanted a host platform for Ubuntu you'd choose something else, and if you wanted platform software for a Chromebook ChromeOS is the right choice.
In the real world, Chromebooks are excellent candidates to install Linux. They are highly compatible, low power, excellent size/weight, and run great. You don't sound like a person who has any real world experience with this topic despite the authoritative tone in your responses.
> ChromeOS has better security and performance than Ubuntu [...]
I'm going to need a citation on that, especially performance. Doubly so if Crostini is put into the mix.
> [...] updates things like peripheral firmware that Ubuntu isn't even aware of.
Like what? WiFi cards, etc.? Isn't that generally in kernel already? What kind of updates do you think are not done by Ubuntu or another Linux distro?
Last I tried ChromeOS was on the Pixel Slate way back when. A buggy, unstable, clearly not properly tested, unperformed mess that I would not wish upon my enemies. Glad to see it has improved to usable now, but that it is better than any other Linux distros, I can't say how considering even being on par with e.g. Fedora would have been a miracle not to long ago.
Happy to admit that purely on the UI/UX, ChromeOS is very solid in my opinion, arguably and subjectively the most consistent and user friendly designed desktop environment I know. Far more consistent than anything MSFT or Apple have provided in quite some time, everything looks like it should, placement is easy to grasp and reliable with a clear identity. Consistency wise, only Gnome can hold a candle to the strictness with which the ChromeOS team execute their vision, though there is the clear divergence in the Gnome team pushing new UX innovations and concepts even if they are controversial and may need to time to learn, whilst the ChromeOS team seems purely focused on the most clearly easy to master approach one can take.
FWIW I'm one of those people. I have an old rotting pixelbook that I installed Linux on back-in-the-day thanks to Mr. Chromebox. It was a huge improvement over chromeos but I'd never buy a chromebook to install Linux on it again because there was too many small annoyances like needing to fix the keymap every time I did a clean install (the caps lock key was bound to super and I vaguely recall some craziness around the higher function keys), and sound didn't work.
This is actually the perfect detail to discuss. ChromeOS printing is literally just CUPS, so it has the same functionality as any other Linux distro. If you have a modern IPP printer on a normal home Wi-Fi, you can expect it to just work. This covers most people's needs.
Where ChromeOS shines is that it has never been affected by severe and numerous CUPS security vulnerabilities like CVEs 2024-47175 through 2024-47177, which were unauthenticated remote vulnerabilities, while Ubuntu and Fedora (and all other major distros) were affected. Why? ChromeOS sandboxes the hell out of these kinds of subsystems. CUPS runs in a PID namespace, network namespace, mount namespace, on a read-only filesystem, with seccomp filters. It cannot use the network, ever. It can only communicate over a pipe with a network proxy. The proxy is only active if and when a user tries to print. The proxy is also in a seccomp jail that prevents it from doing anything except enumerated network traffic and the pipe. The proxy is written in a safer language than CUPS itself, and protects CUPS from malformed, malicious inputs by validating both PPDs and print requests.
I have used Linux for 20 years, but only for development, and I will only develop on Linux.
For everything else (email, files, photos), I want a browser. Used to be Mac/Osx, but got tired of being managed by it.
Just my preference. You can do everything on Linux, just never felt comfortable with it.