Developer's Toolkit

Blog archive

Eclipse Conference Brings Together People, Processes

I had the opportunity last week to represent my employer, Progress Software, at the Eclipse Members Conference in Chicago last week (Fawcette Technical Publications is also an associate member). I was able to attend only the first day of the two-day meeting, which included a quick start meeting for new members, followed by an afternoon-long marketing symposium.

Few of us will get to attend a set of meetings like this; Eclipse members are generally commercial software companies, although there is also a category of member known as a strategic consumer, which is a user organization that pays the membership fees and commits to a certain amount of development effort to support the Eclipse Foundation. And, of course, individual developers can also become active in Eclipse, as individual members or as committers.

But most users of Eclipse don't fall into that category, and may lack the larger perspective of the platform and its goals and direction. The number of major projects being undertaken by Eclipse members is pretty impressive, and includes the various Eclipse Platform projects, the Web Tools project, the Test and Performance Platform, and the Data Tools project.

My sense is that the Eclipse Foundation is remarkably focused on moving Eclipse forward. There seems to be little in the way of ego within the ongoing discussions between the Foundation and its members. Certainly the members have their own agendas for working on Eclipse projects, but the Eclipse approach seems to preclude the worst abuses of vendor lock-in and upgrade hell.

What does this mean for Java developers? First, Eclipse continues to drive down the cost of development tools. The freely available Eclipse tools provide the majority of what developers need to get their jobs done. Free or low-cost plug-ins can provide much of the rest.

Second, Eclipse is keeping the tools vendors honest. There is no way that any one vendor can enforce a feature set or pricing structure that forces developers to pay through the nose. While you have to wonder if any vendor can make this model work for them over the long haul, it is great for developers looking for the best tools at the lowest cost today.

Posted by Peter Varhol on 09/25/2005


comments powered by Disqus

Featured

  • VS Code 1.123 Adds Agent Session Sync, 1M Context Windows

    Microsoft released Visual Studio Code 1.123 on June 3, adding agent-focused features, larger model context support, integrated browser updates and a new delay for some automatic extension updates.

  • Copilot Billing Shock Hits Developers

    Developer complaints about GitHub Copilot's new usage-based billing model have centered on unexpectedly rapid AI credit consumption, and neither GitHub nor Microsoft has responded directly to the backlash, though they have previously published guidance to lessen model usage costs.

  • Hands On with GitHub Copilot App Technical Preview: Turning a Blazor Issue into a PR

    GitHub's brand-new Copilot desktop app, in technical preview, handled a small Blazor issue from planning through pull request creation, but the hands-on test also showed why developers still need to verify agent work in the running app before merging.

  • At Build 2026, Microsoft Sets Up Windows as an OS for AI Agents

    Microsoft's Build 2026 Windows developer announcements point to a broader platform strategy for agentic AI, spanning terminal workflows, local models, app-building skills, Cloud PCs and operating system-level containment.

Subscribe on YouTube