The new Chrome OS "Chromebooks" are right around the corner. And if you're anything like me, the question about how this affects the rest of the Linux ecosystem is a nagging concern for you.
Google has been supportive of Linux on the desktop and various open source applications, and has also pushed to get an iOS alternative into the mainstream with Android on smartphones. Yet, despite these positive considerations, I find myself with reservations about the Chromebook.
It's more of a feeling than anything rational I can point to. After all, the Chromebook is still waiting to be released to the public. So judging the concept too early might be a mistake, even if it does seem like they're taking the Linux kernel into uncharted water.
All signs point to Google
Google's Web applications are as unimpressive as Microsofts attempt to succeed in the search engine market. Both efforts are usable enough, yet each of them fail to offer a clear motivation to get someone to change their existing way of doing things.
So the idea of early adopters being excited about Google's new Chrome OS netbooks seems both premature and completely silly. Especially since it's going to be a limited experience, full of bugs and frustration. It's a beta concept at this stage. Still think I'm concerned over nothing? Consider the following thoughts below.
First of all, you're entrusting your entire computing experience to the Google cloud. Think about this for a moment: according to this Chromebook document, Google accounts are used to sign into the Chromebook. This isn't speculation, rather Google's own claim that a simple Web login is all that protects your privacy from prying eyes.
Google, you've got to be kidding me!
Not only are end-users entrusting their support needs to a Web forum, they'll also be hoping their Google Web accounts are secure. I can't speak for anyone else, but I think I'll pass on placing that much trust in a Web server and a password to handle all my data.
But wait, there's more! Google has also worked hard to make sure that your printer will be completely useless when connected to your new Chromebook. That's right, unless you happen to have an ePrint compatible HP printer, using the Chromebook to print is apparently not an option.
The best part: if you wish to connect to a standard printer at all, you must jump through more hoops and run Windows or OS X on a separate computer. Comically, no Linux support is provided for this separate computer despite the Chrome OS itself being using the Linux kernel to operate.
Potentially a black cloud for Linux
After establishing Google's non-use of Linux printing technologies like CUPS, one has to wonder how these negatives aspects of Chromebook will further effect Linux users! While it's true that one can always choose not to buy a Chromebook, this doesn't change the irritation experienced when trying to follow Google's thinking on dealing with perpherials.
The problem is that instead of customizing a Linux distribution to use different Linux technologies, Google is funneling users into their own applications. To the end-user, this isn't a Linux-based experience on the Chromebook. Instead, it's just some Google-based operating system that makes printing a pain in the backside!
One could even argue that embracing the Chromebook is essentially worse than Google not supporting a Linux desktop experience. To the untrained eye, it seems as if Google is diverting attention and resources away from the Linux desktop and into the Chrome OS way of doing things.
Consequently, any potential for mainstream press going to Ubuntu, Fedora, and OpenSuSE, will instead go to this new Microsoft/Apple competitor known as Chrome OS.
I realize that Google Code and related projects have done tremendous good for the open source community. But instead of borrowing from the work done within this community, Google is choosing to basically work around the fruits from this labor.
Google Code projects aren't some charity group begging for Google's funding. They've been given a chance to serve as part of a larger ecosystem to help Google in the long run. Instead, it feels like the biggest Linux-based aspect is really just the kernel, foregoing many other components that make up the Linux desktop experience. Perhaps there are some related projects being used within the Chrome OS. Unfortunately it's difficult to know this, considering how everything seems to lead to the Chrome experience only.