Is he being satirical? I think it sounds like a good idea.
I think you'll see it come together from two separate places.
1. Standardization of browser event subscription by a remote host. This might happen via an HTML5+ ecmascript API in which scripts register user event callbacks. Think ACPI through JS. This requires aware applications but Google could make it a de facto standard.
2. In-browser identity management and single sign-on. This is necessary to achieve the seamless re-authentication to services. This may be in the form of a browser plugin that, like regularfry says, saves to cloud storage. I think we'll see browsers grow web-aware state APIs in the next 5 years as local and remote get blurrier and blurrier.
It could be argued that the browser itself is ripe to undergo a rather radical change over the next few years. Google's strategy here is to fatten the browser so that it becomes the Operating System, and then offer web-aware apps through that environment. Another strategy would be to thin the browser down and integrate it more strongly into the OS.
Browsers should be managing this kind of continuous (or as I like to say, persistent) state for us. They should also be capable of a lot of the social interaction some companies have chased after - sharing certain information with friends, syncing things up (simple app idea: sync up youtube across multiple browsers so you can fill your house with music simply by having a net connection), and likely other things as well.
I would suggest that people work toward building these browsers of the future, but such an undertaking would be monumental, and as you noted, Google has a pretty strong lock on this corner of the tech world.
Comments
Is he being satirical? I think it sounds like a good idea.
I think you'll see it come together from two separate places.
1. Standardization of browser event subscription by a remote host. This might happen via an HTML5+ ecmascript API in which scripts register user event callbacks. Think ACPI through JS. This requires aware applications but Google could make it a de facto standard.
2. In-browser identity management and single sign-on. This is necessary to achieve the seamless re-authentication to services. This may be in the form of a browser plugin that, like regularfry says, saves to cloud storage. I think we'll see browsers grow web-aware state APIs in the next 5 years as local and remote get blurrier and blurrier.
What do you think?
It could be argued that the browser itself is ripe to undergo a rather radical change over the next few years. Google's strategy here is to fatten the browser so that it becomes the Operating System, and then offer web-aware apps through that environment. Another strategy would be to thin the browser down and integrate it more strongly into the OS.
Browsers should be managing this kind of continuous (or as I like to say, persistent) state for us. They should also be capable of a lot of the social interaction some companies have chased after - sharing certain information with friends, syncing things up (simple app idea: sync up youtube across multiple browsers so you can fill your house with music simply by having a net connection), and likely other things as well.
I would suggest that people work toward building these browsers of the future, but such an undertaking would be monumental, and as you noted, Google has a pretty strong lock on this corner of the tech world.