The Chromebook Pixel Review
by Jason Inofuentes on May 31, 2013 8:00 AM ESTInput
A high pixel density isn’t the only thing special about the display. A capacitive 10-point touch layer is built-in, and though the OS isn’t exactly touch-centric, it is nice to have the option. The reality fo the market, though, is that touchscreens are inevitable. As the price of the technology drops and users become more accustomed to them the barriers to inclusion become nil. It feels gimmicky at times, and the keyboard/mouse schema has never seemed to me like one waiting to be disturbed. But including touch doesn’t detract from the experience, and I found myself putting it to use way more than I expected. Does a site render text too small to read? Resize in a flash. Scrolling through Google Maps looking for something? It’s probably quicker to do it with one finger on the screen than two on the trackpad. Even on-screen buttons are quicker to hit with your finger than by dragging the cursor to them and then tapping, provided the action area is large enough. It wasn’t long after I started using it that it just became the natural reaction. All sorts of buttons are just waiting to be pressed, and it becomes so instinctive that you will spend days after reaching up to lesser equipped screens.
Scrolling and other touchscreen gestures were at one point quite choppy. In the course of this review, though, updates to the software have drastically improved performance to the point I almost prefer it to the touchpad. That said, you’re often not sure what you’ll get when you open up a given app. Sites where a pinch to zoom gesture can have a useful impact, say Google Maps, can implement the appropriate APIs and often are. In sites with responsive designs, zooming can alter layouts for readability, though often that ends up feeling like two processes competing with each other. Pinch to zoom does simply that in less responsive designs, or sites that lock onto a particular layout, such as GMail. These features are hidden behind chrome://flags because they remain a work-in-progress, but I urge any users to turn them on and try them out. You’ll likely forget about that touchpad before long.
Speaking of that touchpad, it remains frustrating that so few players in the notebook space have nailed touchpads. It should be particularly embarrassing to other notebook manufacturers that this is Google’s first attempt, and they’ve done an excellent job. The large glass trackpad offers a novel tactile experience after so much time with Apple’s units, but is no less well performing. Taps and clicks are registered without fail and the scrolling experience with the touchpad is smooth and easy. Once again, the settings to activate more complex gestures on the touchpad are buried deep within chrome://flags/ so they’re not quite ready for primetime. But they offer something that Chrome has dearly needed, real multitasking.
Before I leapt into the world of OS X, or Linux for that matter, I was knee deep in Windows 7. Dozens of tabs spread across four or five browser windows and a few other applications, all in one space. OS X showed me that windows management was distinct from workflow management. The early days of Chrome OS were an experience that, then, felt all too familiar. When the hardware was incapable of handling more than a few tabs, it was easy to be diligent about culling the fat and closing unused pages. Better hardware made clear that something in software needed to be done to better manage the myriad of web apps and pages I could now keep open.
The technique that Google chose is familiar to OS X users, and revolves around that capacious touchpad. Buried in chrome://flags are options for three-finger touchpad gestures. Three finger swipes left and right let you scroll through a given window’s tabs, and three finger swipes up and down let you scroll through the available windows. The window switching is particularly useful and unique; unlike OS X, swipes don’t shift one position at a time, rather allow you to scroll through the open windows like a stack of cards. The gesture is not yet refined and requires some amount of practice to get right. The difference, though, makes this a multi-tasker’s tool.
We’ll end our input discussion with my favorite of all, the keyboard. If the design of the Pixel advances the experience of an all aluminum notebook, the keyboard similarly moves the goal posts. This isn’t a revolutionary component; the keys are a little squarer but the layout isn’t novel. The CapsLock key is once again usurped by the dedicated Search button, which I might actually use more often if it sat where the Start/Option key did. Instead the CTRL and ALT keys are broad on the left side, which does make them easy targets when switching tabs/windows. I was surprised by the mechanical action of the keys. One of the compromises of thin notebook designs is the depth of the keys, and their motions. Laying your fingers on the Pixel’s keys they feel slightly wobbly, and I was expecting a quite squishy typing experience. Instead, though shallow, the keys action is quite refined, with an easy to discern and trigger point that makes precise typing a breeze. The broad palm rests made for a very comfortable typing experience and overall I had no problems clicking away for hours at a time. This fountain of praise for the keyboard ends with the row of function keys. Controls for volume, brightness, window switching and dedicated back, forward and refresh make up this row, and you’ll make haste to find ways to avoid them. The keys are remarkably stiff and their action ill defined so lighter depressions don’t have any effect. Can’t have it all, I guess.
Facebook
Twitter
RSS
74 Comments
View All Comments
Bobs_Your_Uncle - Monday, June 3, 2013 - link
A good review. Also, I thoroughly enjoyed reading various drafts of various segments in the "Why Not Android" segment!seapeople - Monday, June 3, 2013 - link
Certainly this is a review, that, upon revealing itself to me on my computer, it exerts a judgement of thought immediately as it just sits there. Beyond reproach due to a quirky optimism and ostensibly modulated restraint, I find it best to reflect upon this review only as an afterthought, being intertwined betwixt moments of time, as though one instantaneous occurrence is immediately transcended by the jolt of the next occurrence, and occurring not simultaneously, but nearly so as to appear so. Therefore, I follow this review with one of my own, a review of the review, that being so similar in style, serves through ironic prose to indicate the true nature of that which we have been so wonderfully graced with via the AnandTech homepage.wffurr - Wednesday, June 5, 2013 - link
For web development, just hit ctrl-alt-t and then ssh into your server and edit there with vim. Problem solved. Chromebooks are perfect for LAMP/Java/Node/etc. web development. Not so much with the .NET web stack. If my work had an OpenVPN or IPSec endpoint instead of Juniper SSL VPN, I would use one instead of a Macbook.rabbit212 - Thursday, August 1, 2013 - link
I purchased a chromebook pixel and it's touchscreen didn't work. The customer service was horrible. I was told that I needed to wait a week for a replacement chromebook pixel LTE. I was forced to wait 48 hours for an RMA due to the Nexus 7 launch. I will never purchase another Google Play device. Apple is more responsive and get's the concept of customer satisfaction.