The main reason is that Google controls the entire environment on a ChromeOS device (kernel, userland, browser), and ChromeOS is closed source so it's not possible for me to easily know what is going on. > If you believe that having the guest user run their search on a typical Linux, Windows, or macOS machine would be better for their privacy, I would be interested to hear how. In fact, going to in an incognito window pops up a little animated box on the right hand side encouraging me to sign in, so I'd expect there's a good chance that my guest user _would_ sign in if they visit a Google-owned site.

Your scenario is oddly specific - I didn't say anything about a Google search, or about ensuring that the user doesn't log in. Extra hardware like that just makes their offering more difficult for a customer to navigate and understand, not to mention the added support and manufacturing burden on the company's side. My hope was that this is just running on the standard Framework laptop hardware, but it looks like it required a bit of a mainboard redesign, as well as a different input cover and keyboard. Granted, if they believe that this will be a big boost to their bottom line / margins / sustainability, then I'm in favor of it on the grounds of helping make sure Framework is a successful company. I feel like Framework could be spending their time doing much better things.

ChromeOS is just more Google adware/tracking-ware, locking people into the Google ecosystem, and (by default, at least) creating a more locked-down environment than a general-purpose OS would have (not quite iOS or even Android, but still not with the flexibility of a 'mainstream' OS). I hesitated posting this, because I don't want to be too negative, but: ugh.

Google chrome book news