Yesterday Google announced their latest branded hardware product, the Chromebook Pixel. Chromebooks have been inexpensive, lightweight laptops running a special Google operating system based on the Chrome browser. Instead of using native applications like a Mac or PC, or even an Android tablet or iPad, Chromebooks only access web applications. That makes them fast, simple and generally secure.
Until today’s announcement though, Chromebooks had one major flaw — all of them had low resolution screens. The “Pixel” in the new Chromebook’s name refers to it’s new 2560 x 1700, at 239 PPI high resolution screen. That’s in comparison to the 1280 x 800 screen on the Samsung Series 5 Chromebook which I’ve been using since last spring.
Since I’m such heavy user of Google’s cloud tools like Gmail, Calendar and Drive, the Chromebook has always felt natural to me. The lightweight feel and the long battery life more than made up for any challenges caused by a lack of “native” apps. When the I saw announcement about the Pixel, giving me more CPU speed, 1 TB of Google Drive cloud storage (for 3 years), and a much improved touch screen (previous generations lacked touch screens) I was quick to cheer it’s arrival and plan my order.
My enthusiasm was quickly assaulted by feedback and articles arguing against the Pixel.
@stevebanfield maybe you’ve been waiting for it.Pricey; incomplete apps.
— John Ludwig (@jhludwig) February 21, 2013
Reading articles like Gizmodo’s “Every Reason Not to Buy the Google Chromebook Pixel” and GearLive’s “3 reasons why you shouldn’t buy Google’s Chromebook Pixel” made that case that the Pixel was a bad idea, badly implemented. Lots of people are arguing they don’t know anyone who would, or should, by a Pixel. Even a poll in Seattle’s own Geekwire was running 84% again the Pixel (as of this morning).
I disagree (and I’m not alone).
