The following is a guest blog written by David Pinkus, on networkWorld.com, a former high-level Google employee who is now senior vice president of information technology for Universal Technical Institute:
Disclaimer: This is exact replica of original source. Copyrights reserved with networkworld.
I think a lightweight, browser-only operating system has been a long-time coming. It’s the actualization of what the network computer dream has been; albeit with the predictable concessions that the network isn’t always available, and you need something resident on the machine itself to make it useful. But I was still surprised when I heard NPR lead off its Morning Edition newscast with Google’s “Attack on Microsoft.” Is it going to displace the Microsoft Windows desktops in most companies? Is it a harbinger of a new computing model? Here’s what I think we’ll see happen in the next 18-24 months:
Is Google the only one that benefits?
Google obviously benefits from having more users do more searches with Google. This is the “long tail” concept. Even if a particular ad only nets Google a fraction of a penny, with enough of those fractions, those ads create significant income. But others win, too. For hardware vendors, having a free operating system and browser that require minimal support, and come from a brand with a lot of consumer goodwill, is a big win. Consider how a PC OEM will feel if relieved of the support burden and associated costs (both material and to its reputation) simply to help new PC users “get started” with today’s operating systems.
Can Google be counted on to secure its new OS?
I think so. First, there’s the whole open-source-is-more-secure argument. More eyeballs on your source code theoretically means more people looking for vulnerabilities (and exploits). Google could have a leg-up overall. The leaner the operating system, the less things exist that could be compromised.
Will the Chrome OS alienate Android developers?
If Android developers were under the impression that Android would be as available on netbooks as readily as Windows 7, then perhaps, but I think Google’s approach here is simpler. Forget the OS, forget apps, do everything in a browser. Android is when you need more than what a browser does.
Is this different than what other vendors have been doing with various Linux distributions for netbooks or similar devices?
Yes, because it boldly attempts to exclude everything except the browser (although clearly it will have to have some internals, such as wireless configuration, date/time configuration, etc., all no doubt rendered through the browser).
What advantages will the device user see?
Super-fast boot times: This is so long overdue. Recycling my Windows machine still takes 6 minutes. Recycling my Mac is much better (and I do it far less frequently), but lean manufacturing pundits would cite the time it take to restart or boot a computer as the epitome of “waste.”
Even cheaper netbook computers. Now an OEM needs to only worry about a nice screen, an input device of some sort (keyboard or pen or gestures), some resident memory and a robust wireless interface. There is a big form-factor play here though; smaller keyboards can be frustrating for larger hands (dare I say for grown-ups?) but at the same time, since people come in all sizes, maybe it’s time that keyboards came in multiple sizes. Add ruggedization, some fun colors (iPhone accessories clearly prove there is a market for that) and better battery life and I expect we’ll see Chrome OS devices for many members of the family.
The key question here though is “How cheap will they get?”, and what’s the delta between how cheap these devices get and the next device that runs Windows or MacOS.
Less bloated applications. I’m writing this with Google Docs and it is all I need. I don’t need 1000 features in my word processor. I need about 10.
Will the hardware requirement really be all that different?
Chrome is a great browser, but it still needs Google Gears (which it includes), which still needs local storage, and you’ll still want a lot of local cache for other Web assets. So while the total memory footprint of the OS may be smaller, and boot times will improve dramatically; you’ll still need onboard memory (but it’s probably safe to say at this point we can forgo a local hard drive).
What are the obstacles to Google’s success?
Ubiquitous wireless is still a myth. Let’s also note that the data plans for the wireless carriers are still egregiously overpriced for the masses, so we’ll either need to see a dramatic price drop in cellular data plans, or more ubiquitous wireless, which will be great, but we’ll still need robust disconnected support.
Just because it will be open-sourced doesn’t mean it will be great. Open source also doesn’t mean many features will actually find their way back into the OS for most consumers. It does mean that OEMs will be able to extend the OS to support their own hardware, which is a double-edged sword because that can also lead to compatibility problems.
I was in an airport the other day and my iPhone automatically identified that there was a sign-in page for the airport wireless and cached the required fields so that every time I go back into Sky Harbor airport, it automatically signs me into the wireless. There’s this fanaticism about usability that some companies espouse that I’ve not seen in the general open source community.
In the end, I do think this is good for Web developers. They’ll still be tasked with ensuring their Web sites work well for all browsers (which will create opportunities for more development tools to help them), but let’s just say this … it still boggles my mind how many Web sites were designed exclusively for IE.
Will the Google OS appeal to Apple’s customers?
I think there is a wildcard here with Apple. OSX is a stellar operating system; and Apple’s ability to make elegant hardware is still heads-and-shoulders above anybody else out there. And thanks to the iPhone, think of how many new OSX developers there are in the past year alone; If the company was to come out with an OSX-based netbook (and I still have hopes for an Apple game console based on OSX), and you had every one of the App Store developers now writing apps for a portable netbook and/or game console (or even an evolved AppleTV), I think you’d have an unstoppable combination. Google would have to make the case that the browser experience can be just as good as the app experience, and find a way to let all of those “other apps” be cached. I think that’s a big obstacle.
Will it displace Windows in the Enterprise?
Not any time soon. Not enough corporate applications in most companies are Web-based, and in my experience, most users still have a document-centric view of the world. They think that in order to create information, the first step is to launch Microsoft Word. Microsoft has spent the better part of the last two decades ensuring that people think exactly like this, and has worked feverishly to get SharePoint entrenched in every corporate account so that extricating oneself from this “information exists in Microsoft Office documents” becomes a nearly insurmountable task.
So I don’t think the Chrome OS will end Windows desktops in the next few years; I think it will add to the collective total number of Internet devices, and drive some of the changes that may make it possible after a few years to have productivity workers exclusively use a Web-based OS. I still think Google will need several evolutions of the browser and years of re-education (which Microsoft will fight tooth-and-nail) of end-users to prepare them for this switch. Some limited users and companies may be able to make the switch sooner (call centers, etc.) but this will depend on hardware manufacturers providing a support model that gives companies a level of comfort when making this switch.
So clearly, Chrome OS isn’t a windows killer, it’s a new generation of OS developed for diskless type systems and most suitable for MIDs (Mobile internet devices) and other thin clients.