Google’s latest iteration of ChromeOS hardware has very impressively sold-out almost as soon as it went on sale.
The new hardware is attractive for a number of reasons: it’s thin, it’s light, it features a lot of the latest technology like Bluetooth 3.0, USB 3, and dual-antenna a/b/g/n wi-fi (and we know there’s a mobile-wireless version coming soon too).
The coolest feature though is that it does not run on an Intel processor, but rather the Samsung Exynos 5 – an ARM A-15 processor like the kind found in smartphones and tablets! The A-15 is the latest iteration of the ARM design; and the Exynos 5 is a powerful chip with minimal power consumption – so no fans and longer battery life on a thinner, lighter battery.
About 90% of what I do my computers is web-based, such as e-mail, news, blogging, and even working with documents and spreadsheets on Google Drive. So a Chromebook would fill just about all my requirements. The only thing I’d be scared to try is managing my photo & video library or touching up my photos. There’s certainly no reason why a Chromebook couldn’t handle that and software like Aviary proves it possible but I think it will be awhile before we see digiKam ported to a Chrome App and there’s a truly comparable option.
What I can’t wrap my head-around though is why?! I have nothing against ARM-based computers or living my life on-line. But what I don’t understand is why we need another platform? At this point Android is a viable option for a netbook operating system. Chrome (the browser at the heart of ChromeOS) even runs on Android. An Asus Transformer is basically a Netbook running Android. Any Android tablet matched up with a Bluetooth keyboard is basically a netbook.
I’ve said this before, and I’ll keep repeating it as long as I have to: WE DON’T NEED ANOTHER PLATFORM!
Apple offers developers the burden of iOS and OS X. Google offers the burden of Android and Chrome. Microsoft offers the burden of Windows (in it’s many iterations) and Windows 8 new paradigm and Windows RT (all of which multiplied by the burden of traditional libraries or newer .NET libraries). And then of course there’s the waffling RIM that burdens us with the old Blackberry and the promise of BB10; and a flurry of other platforms like Firefox OS, Sailfish, and Tizen.
It’s not surprising that RIM and Microsoft are having trouble attracting developers to their app stores – developers are all sick and tired having new platforms dropped on them like a ton of bricks and being told “if it doesn’t succeed it’s your fault because you didn’t write any killer apps for it!“
So why didn’t Google put Android on this hardware and call it a Nexus NB (for netbook) or Nexus K (for keyboard) or Nexus RT (for Kiss-our-ass-Microsoft)?
As a Chromebook my only interest in purchasing one would be to wipe-out ChromeOS and install ARMedSlack. If it was running Android though I’d be perfectly happy to leave it as is!
Cross-posted on Schultzter’s Blog