[kls]

If I may ask a follow-up, what's your perspective on keeping the pieces and the integration "safe"?

For me, I would like to see the browser sand boxed completely away from the OS, with the cloud this may be a ever closer reality, have drop box like functionality for the browser where if you want to upload a file, you do so from the cloud not your local device. So say I want to send you a picture, I choose the picture from say Picasa or Flicker as opposed to going to my local drive.

I would like to see something like SSL certificates for web providers that want to be able to step past that sandbox. So providers prove their identity to get a certificate that lets browsers access files to upload or native apps are utilized to get content into the cloud. Cutting the filesystem away from the browser is the first step.

Second with HTML 5, there are browser based data stores available to developers. This should be the first option when a developer wants to keep file information on a users system. From there they should offer to save files to the cloud providers. With the way the web is moving, there are less and less legitimate reasons for a web provider to access the native system. If they do, they should be able to justify that reason for a certificate or they should be able to write a native app and supply it via an app store.

Naturally some providers will not like the thought of using an app store, in which case they can offer it for download with a certificate or via a whole lot of security exceptions on the part of the user. Much like Firefox does with a expired SSL certificate where they user has to basically insist that they know what they are doing. I would like to see enterprise controls on that as well, where an IT department can override the user and not allow acceptance of the risk by the user.