Open Web

Apple desktop and iPhone support of Microsoft Exchange is not support for Microsoft, as some think.  It's actually a strategy to erode Microsoft's desktop monopoly.  It's also part of a longer term plan to thwart Microsoft's hopes of leveraging their desktop monopoly into a Web Server monopoly. Excerpt: Apple is reducing its dependance upon Microsoft's client software, weakening Microsoft's ability to hold back and dumb down its Mac offerings at Apple's expense. More importantly, Apple is providing its users with additional options that benefit both Mac users and the open source community. In the software business, Microsoft has long known the importance of owning the client end. It worked hard to displace Netscape's web browser in the late 90s, not because there was any money to be made in giving away browser clients, but because it knew that whoever controlled the client could set up proprietary demands for a specific web server. That's what Netscape had worked to do as it gave away its web browser in hopes that it could make money selling Netscape web servers; Microsoft first took control of the client with Internet Explorer and then began tying its IE client to its own IIS on the server side with features that gave companies reasons to buy all of their server software from Microsoft. As Apple takes over the client end of Exchange, it similarly gains market leverage. First and foremost, the move allows Apple to improve the Exchange experience of Mac users so that business users have no reason not to buy Macs. Secondly, it gives Apple a client audience to market its own server solutions, including MobileMe to individual users and Snow Leopard Server to organizations. In concert with providing Exchange Server support, Apple is also delivering integrated support for its own Exchange alternatives in both MobileMe and with Snow Leopard Server's improved Dovecot email services, Address Book Server, iCal Server, the new Mobile Access secure gateway, and its include

Moving the Point of Assembly Kudos to Zoho. Their efforts remind me of the early days of the Microsoft Productivity Environment where core MSOffice editors expanded their reach through DDE, OLE, rich copy/paste, data binding, merged content and data, VBA scripting and the infamous recorder, and a developer API that meshed platform and productivity apps so deeply into end user information that the binding of business processes to the MOPE is proving near impossible to break. Even for years after the fact. A business ecosystem for client/server was born back in the early 90's, with Microsoft continuing on to own entirely the client side of the equation.

Wow.  Google has re-purposed IE for the Open Web! excerpts: A number of modern Web features cannot be used pervasively on the Internet because Microsoft's dominant browser, Internet Explorer, often fails to support current and emerging standards. Google has a plan to drag IE into the world of modern browsing by building a plugin that will allow it to use Chrome's HTML renderer and high-performance JavaScript engine. Google hopes that delivering Chrome's rendering engine in an IE plugin will provide a pragmatic compromise for users who can't upgrade. Web developers will be able to use an X-UA-Compatible meta tag to specify that their page should be displayed with the Chrome renderer plugin instead of using Internet Explorer's Trident engine. This approach will ensure that the Chrome engine is only used when it is supposed to and that it won't disrupt the browser's handling of legacy Web applications that require IE6 compatibility. Google is opening the source code now to get feedback and assistance with testing. The plugin will include Google's speedy V8 JavaScript engine, support for Canvas, SVG, and all of the other features that users enjoy today in Chrome. That also includes the next-generation CSS rendering features of WebKit such as rounded corners. The pages will look just like they would if they were rendered in Chrome. Google is going much further [than Mozilla] by providing the entire renderer. If the plugin is adopted by a sufficiently broad number of users, then Web developers will never again have to contend with IE's limitations. It could also open the door for adoption of HTML 5 and other important emerging standards.

Interesting strategy. Now if we could just get da Vinci/HTML+ to market ...

Daniel Eran Dilger has compiled a remarkable history of HTML.  One strange thing though.  He gives Microsoft a pass at every turn!  Very odd.  Especially since Dilger is the original fan boy.