Thread: Chrome OS
View Single Post
Capt'n Corrupt's Avatar
Posts: 3,524 | Thanked: 2,958 times | Joined on Oct 2007 @ Delta Quadrant
#12
Originally Posted by Crashdamage View Post
Chrome OS strikes me as not really a new concept at all, but just of a WAN version of 'thin client' computing on a LAN, which was supposed to be the Next Big Thing years ago but has found only limited success. Basically a dumb terminal (= browser) with everything - files, programs, etc. - residing on a central server (= the cloud).

Well, the most of the same problems and limitations of thin clients apply to Chrome OS. Things like...
a. Privacy, security or the Big Brother factor.
b. Reliability. Server down? 'Net down? Cloud services down? Screwed, can't do squat.
c. Adaptability and customization. You're limited to what the cloud offers. No installing whatever and tweaking to suit. Conformity in computing.

Someday Chrome OS or something like it may be a realistic option. IMHO that's many years away. And then only if net neutrality can be maintained and ISPs don't start charging an arm & a leg per GB. Total dependence on heavy 'net usage to do or access anything would give ISPs almost unlimited power to control - well, almost everything. Come to think of it, they have almost that much power now....yowwwza! Scary....
Indeed, very good points. Chrome OS is not a new concept per say, but a novel implementation. But directly to your ponts:

a. It seems with the popularity of services like Google Docs, Gmail, and many, many others, individuals are more less worried about the potential privacy than they feel about the benefits of this convenience.

b. This is also somewhat less of a concern with always improving services, and redundancy in many cases (mobile data, and wired). Once upon a time one could have said the very same about electricity, certainly when it goes out, we're at a stand still. I would be interested to know the broadband reliability based on area.

Another point worth consideration is the offline capabilities of HTML 5 which can be implemented by developers to provide offline usage. How much this feature will be used remains to be seen!

c. This is a power-user feature, but I suspect that Chrome OS is positioned towards the lay person. However, having a service in the 'cloud' doesn't necessary imply little customizability; it all depends on the service. Again, there exists the possibility that power-users can install their own home-servers and serve secure apps.

I think that Chrome OS is still a little early in that there are few apps, but the Google Chrome App store, not only puts apps in a central location for discovery, it monetizes them and provides developer incentive. The reach of the web, the standardization of the web, the extreme proliferation of web servers, and the inclusion of the Chrome App Store, are all features worth notation when comparing this to the thin client concept of old.

I personally believe that this is the future. Ask any regular user what they do on their computer, and they'll generally remark: web surfing, word-processing, music listening, and possibly movie watching. The web can do all of these things, and Chrome OS will push these services and more directly into the users awareness.

If I was confident that I could run Ubuntu from a centralized server, and have access to its apps via a web interface, I would quickly hop on Chrome OS, and get a reasonably powerful central home computer. Performance is my only concern as this sounds very VNC-ish. Of course, if popular projects port to NaCl, I wouldn't hesitate. Having access to my apps via a cheap, thin laptop with excellent battery life, and a convenient tablet, is a very compelling idea.

I'm very confident in one thing, though: Microsoft is fsck'd.
 

The Following User Says Thank You to Capt'n Corrupt For This Useful Post: