Next step in the Chrome OS journey
googleblog.blogspot.com
googleblog.blogspot.com
These laptops sit next to our couch in a stack as a set of floater laptops we use for random surfing. If any of us are just looking for a quick bite of information, we generally pull out the Chromebook rather than walking over to the Macbook that sits on our kitchen counter. The Chromebook is also great for our son to use when building LEGO from PDF instructions.
Browsing is far better on the Chromebook than it is on any Android or Apple device I've used, hands down. I find the browsing experience to be frustrating on an iPad or my Galaxy 10", while the Chromebook experience is flawless. The device is basically ready-to-use for browsing as soon as you lift the lid, in contrast to the fair amount of time it takes to get logged into the Macbook (especially if another user has a few applications open in their session).
The hardware itself in the early models was slightly underpowered, but that doesn't really seem to matter much unless you're playing a particularly intensive Flash video or HTML5 game. Scrolling is fairly slow on complex sites like Google+ as well. For what we use it for, the hardware is pretty decent. The touchpads have also been hit-and-miss in the early models.
What makes these devices a hard sell is the price point. The cheapest Chromebook experience you can get today is the Acer (@ $300). Considering the fact that you are buying a piece of hardware that effectively does less than a laptop, I would find it hard to justify spending that amount if I were looking at hardware today. Even though I prefer to use the Chromebook when surfing over the tablets or the full laptop, I feel like the cost is just too much for a single-purpose device like this.
For Chromebooks to really take off in the home market, I think that a device with the equivalent power to the Samsung Chromebook 5 needs to be on the market at a $199 price point. I could see myself buying them at that price. I don't see the Chromebox being popular in households ever - I believe that we'll see the decline of the non-portable computer going forward at home. Alternatively, if we saw some sort of Android hybrid integration with the Chromebook, I think that this could radically change the equation and add significant perceived value to the device.
Now, if I were running a business where a large subset of employees could get by with just web access, I would definitely consider rolling these out. The Chromebox looks like it could be a real game changer for business.
FWIW, this is not a property of the ChromeBook, but a property of how you choose to use it (which may in turn be a property of its relative cost if anything). My 11" MacBook Air runs two apps (Chrome and iTerm) and I do not leave it locked or logged out. At worst I have to apple-tab to Chrome from iTerm once I open it before I can use it to browse.
The key here I think is an operating system UI built on the understanding that modern applications have both client and server components that are equally important and need to blend together seamlessly.
For example , about 50% of the applications I use are on the web/internet yet my browser is just an application like any other on my launch bar.
At that point just setting up a kiosk can either lead to "we just won't do sales" or spirals into "lets get our partners involved too" which gives you a kiosk designed by committee.
Getting that business license is a small cost compared to getting customers engaged and then pushing them away.
This transition can't happen suddenly. Google may also be waiting for the rest of the mom-and-pop web to catch up with the capabilities of native apps (via WebRTC, WebGL, etc) without having to depend so much on extensions, NaCl plugins and the like. At that point, ChromeOS will "just work" for rich applications alongside the rest of the web, which neatly sidesteps any fragmentation issues.
It's interesting, though.
Also, I could be great for schools for the same reason or for some office workers that just need email and Google Docs.
I think this fits with that other item on Hacker News today about targeting the right user. In this case, for a non power user, this has great potential.
They really need to get the cost of the Chrome devices way down from where they are.
I agree that the cost of Chrome devices needs to be lower, but they need to be priced closer to midrange Android tablets (~250-300$) than Raspberry Pis.
That said, it would be curious to see what kind of processor ends up being optimal for HTML5 content. It's not completely inconceivable that architectures will end up being tuned for JS execution.
And you need to check (or better, run) a few benchmarks before making pronouncements like that. Per-clock, SNB beats the A9 in my OMAP4 phone by about 2x on stuff that fits in the L1 cache, and a bunch more on things that spill out (the phone SoC has absolutely nothing like the L3 cache on SNB).
I think it's very doable. I just don't think the manufacturers want to go that low because they want to exploit the early adopter market, and/or because Google was not ready with support for ARM.
It's not very good when you're running Ubuntu, but then again even my nice i7 laptop can really suck under Linux sometimes. ChromeOS might help.
[1] http://chromeos.hexxeh.net/ [2] http://www.chromium.org/chromium-os/chromium-os-faq#TOC-What...
[1] http://www.chromestory.com/2012/05/samsung-chromebox-price/
[2] http://twitter.com/Tojiro/status/207604697073324032