Eclipse dreams up new schemes of disruption
First five years was a warm up
After turning the Java tools market upside down and putting more than a few people out of work in its first five years, Eclipse hopes to cause more mischief during its next five.
Eclipse executive director Mike Milinkovich has earmarked three burgeoning open source projects in the areas of web development, Web 2.0 and on the desktop he feels could emulate the early success of Eclipse's C/C++ and Java tools.
Speaking on the anniversary of IBM's $40m code donation that made Eclipse, Milinkovich told The Register the goal is to create more successful projects. He highlighted the PHP IDE, AJAX Toolkit Framework and Rich Client Platform (RCP) initiatives as strong contenders.
"Our priorities [in the future] are we want to see a couple of projects at Eclipse become as widely successful... Windows CDT [C/C++ Development Tools Project] and Java tools are there. Our goal is to help nurture more projects," Milinkovich said.
In five short years Eclipse has grown to 150 members, there are an estimated 1,300 Eclipse-based products, and downloads of the Eclipse SDK average 10 times more than rival NetBeans from Sun Microsystems.
Eclipse has challenged the economics of the tools market, forcing at least one vendor out of business and many other big names to get on board or go bust trying to fighting it. Eclipse's growth also forced Sun to step-up the pace on its long-neglected NetBeans once it refused to join the IBM-backed group.
What began as a crudely engineered IBM attempt to undermine Sun's dominance of Java through the Java Community Process (JCP) was quickly seized upon by ISVs and developers as a handy way to reduce IDE R&D.
Eclipse provided a common, open infrastructure for organizations that needed a tools framework but didn't want to spend the time or money building or maintaining an IDE - companies like SAP and SAS, who are members. Hence, rapid growth.
Such was the potential, Eclipse quickly exceeded its Java/CDT remit and moved into lifecycle management, desktop clients and business intelligence. There are now 66 projects.
Eclipse has forced closed-source Java companies to fundamentally re-assess the whole notion of charging a license fee for an IDE. Remember WebGain? Already wounded by questionable management and architectural decisions, WebGain sources told me in 2001 they were shutting down because the company couldn't keep up with the community on innovation or justify charging for tools.
BEA Systems, one of the leading application server vendors pushing its own Java web services "development environment" WebLogic Workshop, and Borland - the Java tools market number-one - woke up to this realty in early 2005 when they became strategic members of Eclipse and announced backing for projects that played to their product and market strengths. Also joining were CA, Sybase and Wind River. That was one Eclipse's pivotal moments according to Milinkovich.
"[Eclipse] has definitely changed their business because it isn't enough to just provide the basics anymore. You can get basics from open source, like Eclipse. If you look at the products that are unique and differentiated from each other, it's on feature sets. There's room to build innovative projects on the platform," Milinkovich said.
Looking ahead, RCP is of major interest to the group. Eclipse is waging a PR war to convince Microsoft developers they should use RCP as it provides backwards compatibility between Windows Vista, due in January, and legacy clients like Windows XP. RCP also helps small ISVs save R&D dollars while broadening their addressable market because RCP applications can be compiled to run on Linux and Mac - not just Windows.
Eclipse cites an Evans Data Corp poll saying 44 per cent of developers have committed to use RCP in the next six months, with "the bulk of respondents in enterprise IT organizations with over 1,000 developers."
"RCP solves a hard problem with style and grace," according to Milinkovich. "It provides a common programming model that gives developers the ability to build rich desktop applications spanning multiple platforms and to integrate those platforms with a mechanism for deployment and management."
The future is not without its challenges, though, and growth is clearly breeding issues. The proliferation of projects and plug ins is putting Eclipse under strain, as developers complain that using too many plug-ins in an Eclipse IDE kills performance levels. Also, it's becoming difficult to see the IDE wood for the plug-in trees.
Eclipse hopes to remedy this with a central web site and rankings designed to help developers find the plug-ins they want. Project Callisto, meanwhile, tries to improve reliability by coordinating different projects to ensure dependent modules are updated simultaneously and work together so developers and ISVs aren't left hanging when new versions of Eclipse ship. Callisto in June wrapped up 23 projects run by 10 teams.
Another problem is quality. An Evans survey of 1,200 developers using 11 IDEs this summer put Eclipse last on quality with NetBeans. That may not be a great surprise given Eclipse was up against premier-level IDEs that have taken years to mature under the stable, project managed environment of a closed-source, enterprise Java vendor. It would explain, though, why Eclipse started Callisto and shows Eclipse's goal now should be refinement instead of extension.
And there's the lingering question over the degree of influence IBM retains. While a benign presence, IBM holds two seats on a board of 12, compared to everybody else's' one. More than 120 of Eclipse's 240 committers are from IBM, although numbers are being diluted as more companies join and new projects are created. And while plug-in providers are flocking to Eclipse, IBM remains the prime beneficiary through WebSphere, Rational and - now - Lotus.
"I'm never going to turn away committers - that would be silly. We are focused on growing the pie so there are more committers," Milinkovich counters.
Perhaps the first five years are just the end of the beginning for Eclipse. Now the hard work really begins.®