Google Chrome OS will have no native apps, data will be stored in the cloud.
techcrunch.com
techcrunch.com
I'd much rather have an OS with the capabilities to sandbox applications, but that can still run an arbitrary binary. For example, I cannot imagine hardware device manufacturers writing drivers that are "cloud apps".
I see Google has videochat in GMail with a browser add-on, perhaps it will come pre-installed with Chrome OS but it would still have little installed base.
An you can't have pay for service like calls to 'real' phones because if the billing was done in the client you could simply remove it, forcing all the billing to be done at their servers - which makes it much more expensive.
An you can't have pay for service like calls to 'real' phones because if the billing was done in the client you could simply remove it, forcing all the billing to be done at their servers - which makes it much more expensive.
You mean like how land lines and cell phones do their billing on the provider's servers and don't do the billing in the phone itself because you could simply remove it?
[edit: this is a beautiful thing http://src.chromium.org/viewvc/chrome/trunk/src/third_party/... ]
My experience is, that for certain tasks, native client application is still much more convenient. Evernote is a classic example - although online version of this note-taking software is available, I still enter a note quicker in native app, which then synchronize the data on the cloud.
It's the same with photo editor, word processor, etc. So, what is really needed are good native applications, which are able to synchronize their data with the cloud. But maybe Google will convince me that web-only platform is better, we will see...
E.g., in my experience, some people have been very vocally opposed to the idea of leaving computers on overnight owing to the energy wastage etc. They were all from Europe, and from precisely the same types of environments where we would usually leave our machines on permanently (eg postgrad university labs).
Not to generalize, but I wonder if (at least at that time) there was not more sensitivity to such environmental issues in Europe.
Unfortunately (at least on PCs) the suspend-resume functionality just has never seemed to work properly ...
I daresay such users would naturally gravitate to whichever environment gets into a usable state the fastest.
I cannot remember the exact number & types of machines I've used or had provided to me at customer premises over the last few years, but I'm pretty sure its > 10. Its only ever been my MBP that wakes up consistently with everything still intact. <= 10% is a pretty poor success rate...
* When I walk in the door at home, it automatically connects to my wireless access point.
* I can ssh into it or scp files to or from it using my laptop (after unsuspending the laptop and waiting for it to get back into X :-O) regardless of where it is physically.
* I use rsnapshot nightly to back it up.
* I tap on the screen and it is "instant on" because it was already on, just the backlight was off.
In short, I never turn it on, I never plug it in (other than to recharge :-()
That is the way Life Should Be (other than needing recharging).
Most people don't realize What Could Be because their computer usage paradigm (imagination) is limited by what Windows + Intel is able to do.
There is a W3C working group: http://www.w3.org/2009/05/DeviceAPICharter, but progress appears pretty slow.
Edit: Just saw the Gears Camera API: http://code.google.com/p/gears/wiki/CameraAPI
Edit 2: The Gears Camera API doesn't seem to actually have been implemented, so I don't know what the plan is.
even though Chrome OS is meant for Netbooks, the number of people that own netbooks and use them to communicate via Messenger, Skype etc is enormous. And people who do use Skype on netbooks will not opt for the Chrome OS because you cannot use Skype in an online application like MSN or Yahoo for example.
Personally I use skype a lot and was looking forward to Chrome OS as a substitute for Windows/Linux on my netbook, and was even considering buying a netbook for my girlfriend just for this purpose, however now I will not be doing that.
Chrome OS supporting only web apps is not like the iPhone only supporting web apps; it's like how the Palm Pre only supports web apps.
They have a disclaimer in the download page: Chrome OS is not related to Google. Service provided by SUSE Studio. See the license.
It's also interesting to note that this was the computing model used 'back in the day.' Everything was dumb terminals logging into a mainframe. Looks like we had it right the first time.
There's always been this kind of pull between putting more smarts at the end points vs having everyone login into one behemoth multivac (mainframe back then, the Internet now). It's obvious that Google is putting its stock in the latter approach. I would go out on a limb and say that computing has been heading in this direction for a long time and companies like msft have slowed it down as long as they can but the flood gates are about to burst open..
This should definitely raise some eyebrows over at W3C.. This is a huge development.
Yep - there's an Apple + MS destroyer right there!
It's a tectonic shift in computing. We're going back to the dumb terminal/mainframe model. Apple will weather it just fine I'm sure b/c they control a shitload of devices. Microsoft will not. If they were dead before, they're worse than dead now.
Google will control the other half of devices but hopefully in a 'non-evil' way. I sincerely hope owning a device with Chrome OS doesn't force a user into using Google services although I'm sure there will be some tie-in.
It's about to get interesting..
What google are proposing is to sell a web browser only appliance - for a limited number of users who only use their windows laptop to run ie this is great, they no longer have to worry about viruses or steal ms-office to write a simple letter.
Google can have many more apps for this than apple, because every website is n 'app', developers can write apps simply using javascript/html - there is no need to buy a mac, learn objective C and join apples dev program and learn what secret signs you need to know to get your app approved.
Google don't need to approve the app in the same way that they don't need to approve your website.
To Microsoft, who make their money from business customers running SQLServer and Windows server licenses, this is about as relevent as Nokia shipping a new edition of symbian.
In any event, I actually have no worries for Microsoft. They have a huge share of the web space already, and are already targeting webapps of their products (even if they have to play catch up, they'll get there).
Apple will have problems because their market consists of people that like their products just to be different and to appear in vogue. When that can be accomplished without buying overpriced hardware, see Apple's share of the PC market drop.
It should be easier for Adobe to make Flash work on Chrome OS than on Linux, though, because Chrome OS doesn't have the diversity of duplicate APIs in normal Linux.
- it's YOUR problem.
Apple offered "web apps" to placate would-be developers and buy time to refine the real SDK and work on the App Store model of delivery. (I know that jailbreakers love to give themselves credit for the SDK, but I think that fails the Principle of Parsimony in the case of Apple, who tends not to disclose things until they're ready, and who holds user experience - which web apps do not provide - above all else.) A lot of people didn't believe an SDK was coming until it was announced, but I don't think any of them really thought it through.
I do believe Google's plan is to make the browser the centerpiece, on the other hand. Their model is to ensure a good web experience, to drive ad revenue, isn't it? Why would they add a native app API?
They already do, chromium comes with native client.
Obviously some apps, notably games, need native access but the initial bitching came from existing Mac developers with Cocoa experience. The big problem For everyone else was lack of access to iPhone hardware features via JavaScript.
If you want your own base cloud, it looks like you'll have to build your own system and ship it.