The author's idea essentially equates to taking the proprietary-ness of plugins and expanding them to the entire browser application. Instead of having a Silver

The author's idea essentially equates to taking the proprietary-ness of plugins and expanding them to the entire browser application. Instead of having a Silverlight plugin and a Flash plugin, we'd have an Adobe browser and Microsoft browser (that's even more proprietary than the current one). At least, that's my idea of it. If the author is suggesting a proprietary application to represent a single web site, that won't fly. I agree on most points - if we want to see really rich web apps, this would be the way to go, and despite existing standards every browser supports proprietary stuff anyway, so we might as well stop fighting it - but the main problem is that users will no longer have a single blue E or swirly red dog on their desktop that they can rely on to bring them everything on the web. Couple this idea with some standards about how all of these different browsers will be made available and standards that require one browser type to be able to open another browser type if the target content better supports the other browser, and maybe we could get somewhere.