Google and its OS
Once more Jason Kottke paints a compelling picture of a possible Google Browser, this post actually being a sort of a second part to the Google OS he mentioned some time ago.
Today at a meeting I was wondering about that scenario precisely, one in which the GoOS were to be used by a significant portion of businesses and individuals: computers permanently on, having stored in RAM all its data and programs, sporting incredibly high connectivity, to all effects inmpervious to physical damage.
Disaster recovery plans actually achievable, through the use of decentralized machines, redundant storage and applications readily available.
Open Source being the paradigm of computing, revenues obtained from service, distribution and other activities with high aggregated value (Such as I cannot explain right now).
Heinlein (and Vernon, at that) maintained that mature technology was easy enough to be replicated everywhere, and although backed by a highly sophisticated theory, that technology would be amazingly simple. That is where the GoOS, and its attendats the browser, GIM and Gmail come about: providing the user with incredible functionality, while at the same time being easy to use and small enough to fit in a disc, or to receive its functionality through the Net via a broadband connection: Imagine an OpenSource word processor from Google, a Gword, working straight out of Gword.google.com, where you could spellcheck, format, apply templates etc. Furthermore, if the power goes out, it is saved in google’s (or your pc’s) cache, and you can have it forever there, no matter where you are, no compatibility problems either. It would always be available.
And, with the advantages of Open Source and the brand recognition of Google, you get all kinds of templates, styles and nifty utilities for your works. How’s that for distributed?