Google are reportedly planning to release an operating system based on their Chrome runtime/browser. If it was anyone else it would probably warrant no interest. The concept itself is not new, but when you consider the timing, the rise of RIAs, Google’s vast offerings and ability to create the future, it deserves a lot more thought.
Update: They have now announced it.
I don’t think I need to re-inforce my position on RIAs being the de-facto applications in future. We’ve all seen the benefits emerge, and we’ve seen their capabilities more than double each year. RIAs run on regular “fat” operating systems very well, and we’ve begun to see them run well on other devices.
I made a switch at some point. From a desktop tower I moved to a laptop, and I have been using them ever since. The reason of course was portability. But this is a physical kind of portability that is really becoming unnecessary through what I like to call device redundancy: having many devices that all overlap in capabilities. Think of the app then the device, not the device then the app.
So now I have my work Mac, and downstairs I have a less powerful computer, well 4 really, all capable of handling non-day-job tasks. A MacBook, an iPod Touch, a Nokia smartphone, an Asus netbook and soon a Flash-enabled TV(?). Almost every one of these is able to access email, Twitter, Facebook, find out restaurant reviews, book cinema tickets, find train times, upload photos. The key is I don’t have to alter my experience a whole lot as I transition between them, because the majority of what I do is through a web app or RIA. If I do need the big guns for anything at all, I open Firefox and type in vnc://workmac and I can control the screen remotely, this is built into OS X.
The only reason the “work” laptop is required is because I am a programmer, a power user, and as such many of the applications have not quite made it to the web, but they almost have, and they certainly will. Of course us power users make up such a small drop in the ocean of what we might classically call computer users, this is vital when considering the feasibility of Google’s OS.
Why Google? Why now?
Google wait, they code, they buy, and then they shock, but they don’t do it via marketing like the others, they do it through an indefensible tour-de-force of truly useful software and services that you simply need.
Of course this is all underpinned by Google Native Client.
The apps: Google have been quietly amassing software for all needs: Search, Maps, Docs (Office), Mail, Picassa (photos), Calendar, Reader (news), Sketchup (3D), and a runtime, Chrome. The reach of their offering, when tied up with a neat cohesive bow clearly infringes on, and actually improves on, what an operating system may offer. Apple for example offer only some of these applications with a new computer, Microsoft even less (although the competition between the two has seen the standard offerings increase each time).
The Cloud: Key to the tenant that the user is now a traveler, a migrant of devices, the cloud provides the synchronisation that turns being up to date from a chore, into an automatic security blanket.
Google have just been filling in the holes, but they are just steps away from a coherent super-stack.
Switching operating systems used to be a big deal, even if you were a geek. Average Joe and Joeline have used Microsoft’s Windows for years, and they may have spent time learning how to use Office. Then came the free “net books”, so cheap and so small they had to have one. But the first netbooks ran a Linux distro. The result was an absolute fail… unfamiliar enough to cause problems, hard to go beyond the surface, so Windows took its place once again.
But things have changed a little due to the migration of applications onto the web. If your only concern in the OS is the browser, you become truly portable. No matter which device you use, from tablet, to phone, to surface computer, your experience is 99% the same conceptually, in terms of terminology and perhaps even in terms of visuals.
This was the promise of Flash, those early pioneers even built virtual operating systems in it, doomed to fail a premature death. After we started to see successful apps built in Flash, a quick succession of alternative techniques emerged include AJAX and Silverlight; (almost) everyone saw the benefits of this model. More than that, this quickly became the primary method of producing an application. Do the numbers, how many web apps are released against desktop.
Google Chrome OS
So it seems now is the time where a lightweight contender with enough focus, and enough driving force could succeed in tipping the balance finally from desktop to web.
If you remember the very first Micrsoft WPF demos, they showed desktop applications which were email-able, inherently connected. At the time I considered these islands in the cloud, whether that was the future of apps, indeed it seemed silly to have to start an OS, to start a web browser, to start an app. Why not cut out the middle man (as does AIR). But this big old web-browser kept on being too useful, too good at connecting the dots, so it lingers. When you turn *it* into the OS, that doesn’t cut out the middle man, it cuts out the old guy that was behind him. Indeed most people don’t even know what the browser is/was.
Google Chrome OS is nothing new, from the Pogo of the 90’s, to linux netbooks of this decade, to the Crunchpad of next, we’ve seen these light-weight alternatives come and go, but this is a war of attrition, and it’s the users that are the grains of sand wearing down at the walls of the Fat Operating System, not the technology.