Opinion: Vendors can learn a lot from Mozilla's
When the Mozilla Foundation recently announced its one-year anniversary, I thought, "Wait a minute! Hasnt Mozilla been around for many years?" I then realized that the anniversary referred not to the Mozilla browser but to when the browser was freed from its corporate entanglements with Netscape/AOL and the Mozilla Foundation itself was formed as an independent entity. As companies from Sun to even Microsoft think about open-sourcing some of their products, they would do well to remember Mozillas history and learn from its successes and mistakes.
Recent weeks have seen some major advancements for the Mozilla browser, as the latest security hole in Microsofts aging Internet Explorer became the straw that broke the camels back for many users.
Given that these users turned more often than not to Mozilla, it seems like a good time to look at the history of the Mozilla project, one of the most significant technologies to make the transition from proprietary commercial product to open source.
In 1998, in what was rightly seen as an act of desperation, Netscape announced that it would open-source its Navigator browser technology as the Mozilla project. However, Navigator itself never did go open sourcethe Netscape developers leading the Mozilla project determined that Navigators bloated code would make it impossible for them to make necessary advancements.
The developers thus decided to scrap the Navigator code and build a Mozilla browser from scratch. This was the right move as far as the browser was concerned, but it sounded the death knell for Netscape.
The Mozilla project saw a delay of two years, during which Netscape made mistake after mistake. One of the biggest was that the Mozilla project was never fully freed from Netscape. Most of the developers and support for the project came from Netscape, so the Mozilla developers, not surprisingly, were sensitive to Netscapes wishes. Unfortunately, these wishes served to set back the adoption and spread of the Mozilla browser by at least two more years.
Probably the most damaging decision Netscape made was to target Mozilla at developers and the next-generation Netscape browser suite at users, with the idea that advances made to Mozilla would eventually make their way into the suite. This turned users off to Mozilla even though it was functionally superior to its sister product.
Netscape then used early Mozilla code in its Netscape 6.0 browser. This proved to be a disaster (we called 6.0 "buggy and slow" in a review) that mainly served to cement IEs place at the top of the browser chain.
Next Page: King of the browser hill.
Jim Rapoza, Chief Technology Analyst, eWEEK.For nearly fifteen years, Jim Rapoza has evaluated products and technologies in almost every technology category for eWEEK. Mr Rapoza's current technology focus is on all categories of emerging information technology though he continues to focus on core technology areas that include: content management systems, portal applications, Web publishing tools and security. Mr. Rapoza has coordinated several evaluations at enterprise organizations, including USA Today and The Prudential, to measure the capability of products and services under real-world conditions and against real-world criteria. Jim Rapoza's award-winning weekly column, Tech Directions, delves into all areas of technologies and the challenges of managing and deploying technology today.