Thanks for your response, it's very helpful. I'll check out the HP Elite Dragonfly too.

As the sibling commenter mentioned, though, Google did just shut down their Pixelbook division, which is what I was referring to. And as a corollary, if you can forward this to anyone that matters, Google's product marketing is the absolute worst. And I say this as a big fan of Google's developer-focused products. Case in point, I'm a giant Pixelbook fan. If Google is shutting down Pixelbook development, why can't Google just put something on their store to point to alternatives, like you have?

As another example, I am heavily invested in GCP, and I'm a big Firebase fan. Yet I can hardly think of any other company that sells to enterprises that is so loath to even show a hint of what's on their roadmap. I get it, priorities can change, and you don't want to put something out there that is (incorrectly) taken as a promise. But tons of other companies have to deal with this problem, and with Google it's almost impossible to get any status about important bug fixes or feature requests.

> Google's product marketing is the absolute worst

As long as ‘killed by Google’ continues to be a well-known meme, they could have the best marketing department in the universe and it wouldn’t make a lick of difference..

That's pretty silly. I know you're exaggerating a bit, but marketing is in the business of public perception. If google took steps to reverse the trend, and the marketing department could highlight that, that would kill the meme.

Hence

> As long as ‘killed by Google’ continues to be a well-known meme

As long as the fire continues to burn, the best firefighters in the world couldn't extinguish it.

But the marketing departement isn’t the firefighters. They’re the marketing of the parks departement. Once the firefighters put the fire out (Google engineering stops haphazardly killing products), marketing can attract people to the parks again (Google marketing attracts people to their services).

I feel like I'm missing some information here. Is it the engineering team that kills projects? I would think whoever's controlling the funding has their hand on the plug...

Google just killed the Pixelbook division https://arstechnica.com/gadgets/2022/09/google-hardware-repo...

I think that makes sense though—partnering with companies like Framework and HP to get the hardware right while refocusing on the software experiencing in-house doesn't mean they don't believe in the market fit for the Pixelbook or the technologies that powered it, it just means that there was enough interest externally that Google doesn't need to take on the hardware complexity/supply chain risk/etc. Partnering with other companies that are already experts in that seems better then trying to get everything right themselves from scratch

(Disclaimer: I have not been following the Pixelbook news or really even considered the device before today, but people on this forum seem to like it)

Your comment is exactly the kind of false dichotomy that isn't really helpful in a discussion.

> If you're a paranoid weirdo

Sometimes it's better to be paranoid (c).

Guess Google isn't a bad case for.

Sorry, I'm not sure I believe this.

I have a Pixelbook that still gets ChromeOS updates regularly- the Android and "Linux on ChromeOS" features are still half baked. After wakeup - Android apps hang or show empty windows, Terminal takes minutes to work, and a reboot usually fixes everything. (This is after a powerwash and being on the stable channel)

I think the hard thing here is that they want to keep the Linux VMs totally isolated from ChromeOS itself, so that they aren't opening up users to attacks. This is taking a lot of effort to get right.

I will say, the Pixelbook was super underpowered. They use the ultra-portable Intel CPUs that have a TDP of 7W, which makes them super slow with anything CPU intensive. The Dragonfly chrombook has a 15W base power usage, and can boost up to 55W, which allows for way more CPU intensive operations.

Yeah, they are half-baked in that they are trying to be a VM for Android and Linux apps, and neither are perfect yet. As far as I can tell, both are still receiving attention.

You might be thinking of the Pixelbook Go with the Intel m3? My Pixelbook (from 2018) is an i5, and performs fine.

They're right. I loved my Pixelbook (non-Go), but the Core i5[1] and i7[2] used pretty underpowered 7W CPUs.

1. https://www.intel.com/content/www/us/en/products/sku/97461/i...

2. https://ark.intel.com/content/www/us/en/ark/products/95441/i...

Yep, this is why saying "an i5" is meaningless. It covers everything from "weaker than a modern phone" to desktop CPUs that pull 150W and perform as such.

It also covers models introduced from 2009 through today. It gives you an idea of how it was placed in the product lineup when it was launched, but not which product lineup, so... not very helpful.

I've never heard of anyone complaining that the OG Pixelbook was underpowered. Even today, it runs Chrome just fine.

it says running VM for Android is heavy

I agree - some of the updates I've received have been so half baked, including the Android apps forever-hang, that I wondered if anyone real was involved in this release. I finally got rid of my chromebook for a pittance because I just got tired of the mess.

The Dragonfly is indeed a nice, albeit pricey, Chromebook. Great to have what looks like a comparable machine for much less.

I’m seriously tempted by this. I’m not a chrome user today; I have heard that when MV3 comes out, I won’t be able to use adblockers in Chrome. Is that right?

After spending £2k on a high end HP x360 only three years ago, and suffering since from horrid thermal throttling, crazy loud constant fans, terrible battery life (2.5 hours at almost idle light web browsing usage) and a spicy pillow battery, followed by being ghosted by their tech support (three attempts to contact) and finally discovering via YouTube that they don't even supply battery replacements for this model, I can only recommend you stay as far away from HP as possible.