The Fixes That Google Chrome OS Still Needs To Make

CowboyRobot writes "Thomas Claburn at Information Week opines that Google's Chrome OS is actually morphing into the Windows-style os that it intended to make obsolete. There's still room to grow, and here are his suggestions for how to make it better: Get better hardware, Include a Web-based IDE, Support local storage, Allow offline apps. 'When Chrome OS was launched in 2010, Google SVP of Chrome and apps Sundar Pichai declared, "Chrome OS is nothing but the Web." Now, if you peer behind the browser pane, it's clear that Chrome OS is looking beyond the Web. It's not a complete repudiation of Google's bet on the appeal of a thin-client system that keeps user data in the cloud. But it is a concession to the realities of a market that's more comfortable with the familiar desktop metaphor.'"

Comments

Chrome already supports most of that

[The MAZZTer]

Local storage via several APIs (virtual filesystem, SQL database, simple localStorage) and offline apps (HTML5 offline, completely locally installed apps, and recently storing any file on the virtual filesystem was added) are already fully supported. Just because no one is making them doesn't make it Google's fault. There are a few Web based IDEs out there, assuming stuff like Cloud9 and jsFiddle. As for better hardware, Google seems to have already upped the hardware from their initial spec (Cr-48 is not getting Chrome 19, I can only assume it doesn't meet the requirements).

No big surprises in the article.

[DuckDodgers]

I think his laundry list of recommended changes is obvious to anyone that's been paying attention.

1. Better hardware. No kidding - right now Chrome OS is aimed at schools and businesses, which if they need a locked down browser environment should be okay with what they have now. But if they want consumer adaptation, offer at least the option of better hardware. I'll buy a Chomebook when I can get Sandy Bridge or a Tegra 4 (yes, I meant 4) processor and a graphics chip that supports at least one external monitor and really good WebGL.

2. Web-based IDE. Again, I think this would spur power user adoption of Chrome OS, though I consider this the least essential of the features.

3. Support local storage. No kidding. It will be a while before HTML5 storage is available at all the websites people routinely use.

4. Offline apps. No kidding yet again. I don't want my device to be useless for my family every time our internet connection has a hiccup.

Re:No big surprises in the article.

[mcgrew]

I don't like the "thin client" at all. "Thin clients" used to be called "terminals". We moved away from terminals to PCs for very good reasons, such as if the network or server goes down you can still get work done. You're not beholden to the server's rules.

Lots of IT people like thin clients because it means job security and control of users.

I'll stick with Linux and my own network. The internet and networks in general are for sharing data, nothing more.

Re:No big surprises in the article.

[Altanar]

The internet and networks in general are for sharing data, nothing more.

Funny. Sharing data is 99% of my computer use. Without the Internet, I might as well not own a computer.

ipad killed the chromebook

[alen]

i was a CR-48 beta tester and never figured out the point of it. they look like laptops but the OS is gimped. yet cost the same as a netbook. what is the point of buying one?

the ipad does more which is why apple is selling every one they make

Suggested improvement: kill Chrome OS...

[sootman]

... and devote the resources to something else. Seriously. The market for "I need a laptop that can run a browser and nothing else" is 1) ridiculously small and 2) can be fulfilled with nothing more than a properly-configured Linux distro. Netbooks, while popular in some areas, were NOT the sales success that many people thought they would be. An even more limited netbook will not likely fare better.*

Laptops are already pretty cheap. The theoretical savings of making a stripped-down laptop that just runs a browser are not offset the costs of such low-volume production.

Tablets are the way to go. The market has spoken. "Simplicity" in computing does not mean "I want to run everything in a browser", it means "I want to click giant icons and run one, fullscreen, sandboxed app at a time." Sorry, Chrome OS team--you went the wrong direction.

In other news, I literally LOLed when some guy at Google was talking about how a Chromebook (that is, one particular piece of hardware) would actually "get faster over time" due to its automatic software updates (which would presumably bring increased efficiency and performance.) BULL SHIT. Why is the Web largely unusable on anything less than 1 GHz anymore? Oh right, because web pages are getting fatter all the time! Does anyone REALLY think that Google will make the OS more efficient faster than web pages will become more bloated?

Seriously Google: KILL THAT SHIT and let those employees work on something worthwhile.

* and before anyone mentions the iPad: yes, it is more limited in some ways, but it's also more powerful in others. On the other hand, I can't think of a single thing a Chromebook can do that a Netbook can't also do, but a Netbook can do literally everything that any other computer can do, while Chromebooks are limited to "I can do some things that happen within a browser."

Re:Data capacity of offline apps

[Danzigism]

I love the CR-48. However I have mine running FreeBSD-9.0 with Fluxbox. All the hardware surprisingly works. When I had Chrome OS on there, it ran very well. People tend to forget that these things run Linux, so if you want actual programs physically installed to the hard drive, then put the sucker in developer mode and get crankin. However to give this functionality to your average Joe who knows nothing of computers, defeats the entire purpose of these devices. The only people complaining are the savvy users anyway.