Skip to main content

Imagine...an internet based world

Was reading "The Google Story", when i got this wierd idea.


Consider a stripped down version of Linux, meant only for doing simple things such as browsing the internet, to read from the various drives (which is primarily meant only for storage of personal data), to play music and some single-player games.
All the rest provided by the internet. Information searching/Chatting/Mailing/Documentation editing/journal maintenance/daily schedule maintenance/news/rss/shopping, etc. What else will you use for your computer for?


Ok, actually i have been working on mainframes for some time now and am getting adjusted to the "dumb terminal" concept. Then i started associating the concept with scenario we are observing all over the net.


As a matter of fact this will reduce the power of processing required on the client side also!!! Looks like the world is changing.... for the bettter, yup, i am sure.

technorati tags: , ,



Comments

Kishore said…
Wow! Talk of a Web OS.. u just buy a device and the moment u hook on, u have world at ur feet... and having said that, it is not that highly difficult either... tell u what, this is one great business opportunity...
Sachin Nayak said…
How abt quitting to implement this revolutionary idea??? U quit, i ll join you soon.
Rohan said…
Sachin and his crazy ideas.
I was wondering, how would you control viruses?

He he.. I am not a geek in OS concepts. In fact, I am technically ZERO.. That's why I work for the world's third best software company..

Popular posts from this blog

So you have your website deployed in PROD ... now what ??

Posting on behalf of Usr.Web.Speed - My previous job had been to architect and develop websites for various customers. During that time my team and I have architected and developed various web applications mainly for enterprises. (But below info is not restricted to enterprises) Other than the usual development and testing tasks involved, our focus area was to abide by multiple SLAs. One of the primary SLAs was to provide the users of our websites a very low (usually subsecond) response time (or page load time). To adhere to this SLA, we did multiple activities, in code, process as well as infrastructure. These include (but not limit to) - Using best practices including (http://developer.yahoo.com/performance/rules.html) Determining the optimum number of calls to the databases, open connections, etc. Providing the fastest mechanisms to download associated content (such as stylesheets, JS files, etc. over CDN) And debugging the reason for the slowness of the websites, when ...