I had a low-end Chromebook that I bought to put Linux on it. Part of the reason for this was that I needed a wi-fi repeater and extra screen for my dev machine.
A long time later my needs changed and I switched back to running ChromeOS. This install was because I wanted to gift the Chromebook to a friend. So we tested YouTube and the Chromebook was mute. It turned out that installing Linux fried something inside and only a new motherboard would fix that.
Luckily I was still on the right side of the warranty expiring, therefore, with no love for the shop I bought it from, I decided to try my luck at getting it repaired. The machine came back box fresh with superb sound. So I was able to gift a 'brand new' machine (which happens to still be on sale) rather than some hand-me down.
I am still on Chromebook Pixel 2013 vintage and very happy with it, the Pixelbook was 'meh' to me even though I think I really need one. I was disappointed that they did not go 8th generation Intel with the CPU during this year's product launches for the Pixelbook. So I am now viewing my Pixel (2013) as a future classic, not that computers have this status (Apple 1, Altair excepted). I think Pixelbooks will also have this status but I don't see an 'investment opportunity' in getting one in the hope it will be worth $$$ in decades to come.
It is not the hardware that is a problem with Google products, there is no 'you must be holding it wrong' nonsense. The problem Google have is in the support. Utterly awful. They have absolutely no idea, as if they are not able to empathise with the customer in any way whatsoever. A budgerigar is as much help.
Fortunately my five year old Pixel is as good as new, not a scratch. Despite its age it still impresses people whether they know what it is or not. Few computers do that these days. The wow factor isn't quite up to 'SGI' standards but I always say it is just 'a cheap really old Chromebook'.
The room filling sound from the speakers under the keyboard is something I can't believe the newer Pixelbook has to quite the same level of 'high fidelity', I would be gutted if that died due to some upgrade. This won't happen though as updates no longer happen (as of a week ago) due to the age of it.
The 2560x1700 'retina plus' native screen mode is also a true delight, particularly with dev tools open. People struggle to read the text and, with them not used to having pinch-to-zoom on their Applebooks, they are amazed that the zoom works just like on a phone.
I have a $3K Dell XPS 9550 on which I run Debian. One of the things many reviewers noted was "wow those inbuilt speakers are loud". And indeed they are loud, it turned out too loud as they burn out. The fix from Dell was new Windows drivers.
As a consequence I've had my speakers replaced under warranty twice now. The second time I swear it was only seconds before I frantically turned the sound down. Alas it was too late. I can't imagine Dell replacing them for free more many few times, so now I'm paranoid about what is really a hardware bug.
sudo crossystem dev_enable_udc=1
It's a PITA, but you can always enable USB, set your device to TCPIP, connect via network, and then turn off dev_enable_udc=0, and reboot...
Well known error: https://www.dell.com/community/Laptops-General-Read-Only/bcm...
At one point, the crashes even managed to corrupt my filesystem. What I will say is that it's super easy to swap out the wifi and M.2 SSD - took 2 screwdrivers and about 10 minutes. I may have lost Miracast but does anyone actually use that?
What languages can you program in?
Bash?
Is Docker running natively?
My head is spinning. I don't want to buy a MacBook, but I'm unhappy with the polish of the Linux world. Is ChromeOS a legitimate alternative?
Current limitations: you don't get accelerated graphics, no sound, and can't access USB or SD storage from the Linux container (yet). Things that look really good, you can install .apt packages from the Chrome file manager, and anything with a .desktop file shows up in the Chrome launcher. Looks like there are a bunch of patches with accelerated graphics coming in, and audio should be coming sometime too. Better storage should be available once they re-baseline on kernel version 4.18+, as that has non-root fuse mounts.
BTW, the reason for a lot of limitations of for security, so that a Linux app can't possibly negatively affect the rest of the system. For that reason, they don't have a mechanism to run Linux programs on system startup -- you have to purposely launch any apps.
But the sound issues, sigh.
It makes ChromeOS into a really powerful terminal. You can run stuff locally that's best to be run locally. Then you can run applications that don't run locally (like that need access to special hardware like a gpu) on the machine itself via x11 forwarding. It's very flexible and works.
As a separate issue from mine (faulty ChromeOS sound), currently you can't use the sound hardware inside the container. But that'll get fixed soon. Just means there is no way to run Linux music making apps yet.
* Based on Gentoo- it was actually based on Ubuntu during development, and I believe it switched to a Debian base (from Gentoo) a year or two ago.
* A slapped on browser - it's a lot more than that. It has its own window manager and many other things. It's closer to normal Linux than Android is, but there's quite a lot of differences.
* Toggling Linux apps on - you have been able to install a chroot unofficially and can run Linux apps that way, but integration with the GUI is pretty janky. Official support for Linux apps is very new and not supported on a lot of hardware.
* Install another distro - not always an option. A lot of the machines have spotty driver and/or firmware support, e.g. my Acer Chromebook is a big headache to get working. Some are supported pretty well though.
I wouldn't be surprised if these problems intersect continuing DRM clampdown efforts. (I've no actual knowledge of what is going on -- just suspicions based upon product designs and behaviors.)
ChromeOS could be really big, and it makes sense as a brand to switch again from Android for the reason.
But, the fact that I lose access to the sound services almost every single time I use the machine is crazy.
The response from Google is not encouraging.
https://productforums.google.com/forum/?noredirect=true#!top...
Basically:
Reboot
Or, just wipe all your data!
If they really expect people to use these as their primary machines or even as just a browsing device, you MUST have sound working 100% of the time.
Mine is setup as a developer machine so it could be that I'm bleeding edge. But I'm loathe to switch back, lose all my data, just to see if that fixes things.