Linked by Thom Holwerda on Mon 8th Sep 2008 20:55 UTC, submitted by Punktyras
Permalink for comment 329707
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.





Member since:
2006-09-27
There's still eyeOS:
http://eyeos.org
BTW, this concept of Web-OS is something you install in a server and access from any browser. The server is then the analog of your computer, where you install all your stuff. Chrome is more like a Cloud-OS, since there's no unique place where your programs and data are. It's more appropriate for SAAS.
Some are objecting to the use of the word "Operating system" for this kind of platforms. That's a matter of terminology. Strictly speaking they are probably correct, but what counts is what the platform is, the thing that application developers target. If Chrome becomes the platform, then the OS becomes like a driver, just and "implementation detail", as Sebastian Kuegler from KDE put it.
What would be desirable, then, is to cut off a few layers of the stack. Decide what the desired platform and behavior is, and then get it as close to the metal as possible. An example of that is the 9p protocol from Plan9. I mean, if we want computers to be wired to each other, why are their communication protocols so verbous?