A Month with the Chromebook Pixel

June 26th, 2013 · 8:09 am @   -  No Comments

Last month, I had the pleasure of attending Google I/O – Google’s annual developer conference and product geekfest. To put it simply, it was probably the nerdiest conference I’ve been to (and yours truly has been to some really nerdy conferences) with Google Glass users everywhere and flying, internet-controlled, camera-connected dirigible floating above the conference floor among the attractions.

One of the things that Google tried to emphasize to I/O attendees was the growing idea of Chrome, Google’s web browser, as a key platform for developers to embrace. Part of that message, of course, came from the talks and sessions where Google promoted Chrome’s widespread adoption (if you count mobile deployments, Google claims 750 million users worldwide) and proudly touted Chrome’s support of both sophisticated open technologies like HTML5, WebRTC, and WebGL, as well as proprietary-to-Chrome technologies like Native Client and their new Packaged Apps capability.

Equally (or perhaps more) effective was the conference’s giveaway of its Chromebook Pixel (not to mention some pretty interesting artistic displays showing off the device and its capabilities, see below).

image

My generally positive take on the Pixel’s predecessor Samsung’s Series 5 Chromebook is one of the more popular posts on this blog and so I thought I would share my take on Google’s latest and greatest. In a nutshell, I will say that the Chromebook Pixel is light years ahead of its predecessors and is an amazing device which hints at the potential of well-built Chrome OS hardware, albeit one which is probably not worth the $1200+ price tag:

  • Good, not good enough, performance: While the Series 5 routinely stumbled and hiccuped, the dual-core Ivy Bridge processor in the Pixel, while not the fastest chip around, was up to the task of almost any large web workload I threw at it – multiple tabs with Netflix and complex webapps like Tweetdeck and Gmail and Feedly running. Even Evernote, which I had not been able to get working on the older Chromebook, worked without any problems on the Pixel.
  • Amazing display: In the same way that other remarkably high resolution displays make you want to view more content (Nexus 10, Retina Display Macbook Pros), the Pixel has actually managed to steal web browsing and video watching time from my tablets, something I didn’t expect would happen.
  • Touch: I used to be a big skeptic of the importance of touchscreen displays on laptop form factors – no more. As cheesy as it sounds, the type of relationship you have with content is different when you can use touch gestures to zoom in/out and scroll up/down versus using arrow keys or a mouse. I can’t say that I primarily use the touchscreen in navigation, but it’s a nice touch (pun intended).
  • Much better industrial design: I don’t claim to be an ID expert, but the attention to detail on the machine is decidedly impressive for a company that many in the tech industry for years felt just didn’t care about design quality. The touchpad beats most of what the PC industry has put out in feel and responsiveness (although that’s a low bar to beat) and, taking a page from Apple’s playbook, supports multi-finger gestures. The device body is smooth aluminum with only a groove on the body for cool-looking LED lights to come out as a signal that the device is on and an interesting piano hinge for the display which someone engineered to function not only as a hinge but as a heat sink and Wi-Fi antenna. Simply put: it doesn’t feel or look cheap.

Couple that with the advantages I described to all Chrome OS systems (rapid boot, easy multi-user support, frequent and automatic updates, syncing tabs/histories/passwords with all your other Chrome browsers), and I think you have a fairly compelling device.

That said, three major problems are worth calling attention towards:

  • This is still just a browser: granted, most of what we do today is in or can easily be replaced by web-based applications of some form or the other, but, this won’t be playing Starcraft or running Excel or operating a server or doing software build work.
  • Underwhelming Battery life: for an operating system that is effectively a browser, I am surprised that my typical battery life is somewhere in the 3-4 hour range, and significantly lower if I’m using Netflix or YouTube. I can’t tell if this is simply an issue where Google included too small of a battery to save costs, if this is the energy from the extra processing power and backlight needed to run such a high-resolution screen, or if this is a operating system/firmware bug where the video codecs aren’t being used properly, but this is something that will likely need real improvement.
  • Extremely high price: while this is a fantastic device, its usage limitations (to basically being a big browser) and storage and memory and battery life limitations don’t make this a $1200+ machine. Interestingly, I do feel that if they included a dual-boot to Linux option, the screen and industrial design could very well justify a higher price (compare with Linux laptop vendor System76’s new Galago UltraPro)

So, the verdict? I am extremely happy I got this device for free from Google. It’s something I use regularly because it is a delight to use and really does put forward Chrome in a fantastic light for developers (which is really the purpose of the giveaway at Google I/O). This device is also probably more than enough for what the average computer user needs (who is mainly interested in checking email, reading articles, watching videos, and playing webgames) and has unique advantages for enterprise/educational settings. But, the fact that Chrome OS still can’t do everything that I need it to do and has limitations in battery life and storage and memory make it difficult to justify the high price for a regular consumer purchase.

Any other Chromebook Pixel users out there care to share their perspectives?

Tags: , , , , , , , , , , ,