<body><script type="text/javascript"> function setAttributeOnload(object, attribute, val) { if(window.addEventListener) { window.addEventListener('load', function(){ object[attribute] = val; }, false); } else { window.attachEvent('onload', function(){ object[attribute] = val; }); } } </script> <div id="navbar-iframe-container"></div> <script type="text/javascript" src="https://apis.google.com/js/plusone.js"></script> <script type="text/javascript"> gapi.load("gapi.iframes:gapi.iframes.style.bubble", function() { if (gapi.iframes && gapi.iframes.getContext) { gapi.iframes.getContext().openChild({ url: 'https://www.blogger.com/navbar.g?targetBlogID\x3d6566853\x26blogName\x3d1%25+inspiration\x26publishMode\x3dPUBLISH_MODE_BLOGSPOT\x26navbarType\x3dBLUE\x26layoutType\x3dCLASSIC\x26searchRoot\x3dhttps://patke.blogspot.com/search\x26blogLocale\x3den\x26v\x3d2\x26homepageUrl\x3dhttp://patke.blogspot.com/\x26vt\x3d2795022480681574377', where: document.getElementById("navbar-iframe-container"), id: "navbar-iframe" }); } }); </script>

Wednesday, September 03, 2008

So Google has released and new browser and some people think it will have 20% market share in 2 years.

I doubt it.

Chrome's biggest selling point is that it provides a rich environment from applications. ...of course, it is probably no where near as rich as ActiveX controls which where created it, what, 1998? So sorry Google, you are 10 years behind MSFT on this one. And what's worse, you don't seem to have learned from their mistakes.

ActiveX controls for IE were largely a failure. But why? They provided easy, rich development of web applications. In fact, ActiveX controls are still the only way to provide a truely rich web experience. Sure, security was an issue but this will always be the case for any application that is "reasonably powerful". So why did ActiveX fail?

I will give you a hint. Why did HTML succeed? Why did java succeed? Answer: write once, run anywhere. It is very easy to write "applications" in these languages which run in 99% of browsers. Sure, there are some browser compatibility issues, but nothing that can't be overcome in a day or two.

But Google Chrome is different. It installs with a default set of API's that your application CAN'T USE. ...unless of course you are building it specifically for Google Chrome. .000001% of the market. Good luck with that.

...and once you take away the API's, what are you left with? A new browser skin. Whoopie.

BONUS: What is microsoft's solution to the "Web OS" problem? Silverlight. Write once, run anywhere. Expect a Silverlight for Chrome in the not too distant future - assuming Chrome is not a complete flop.

Comments: Post a Comment