Eclipse, Visual Studio, NetBeans and WebSphere

One of my colleagues, an experienced Visual Studio developer, recently had a look at IBM’s Websphere development environment and was enamoured by it. I think he would be interested in what the industry is saying about Eclipse (and NetBeans for that matter). I wasn’t wrong, in pointing him towards Eclipse, was I? 😉

  • IBM Websphere and Eclipse – describes “The IBM WebSphere Studio development environment extends Eclipse technology to a whole new level, integrating enterprise-level project management, advanced Java development, visual editors, extensive Web infrastructure management, and Web services support, to name a few, within a flexible open architecture.
  • Eclipse Casts Shadow on Sun – Darryl K Taft on 20 May 2005 reported, «a Microsoft source said: “The game is not over, but when we think of developer ecosystems other than Visual Studio we think Eclipse. We don’t think NetBeans.” … Pat Kerpan, Borland’s chief technology officer, said Eclipse “might be the end of the constant retooling we’ve gone through over the years. … This could be the beginning of a framework that will live across multiple epochs to come.” … Forrester’s Zetie added: “There’s no doubt in my mind that as far as enterprise developers are concerned, Eclipse has won—at least outside of Microsoft’s sphere of influence—with major tools vendors such as Actuate, Borland, BEA and Sybase lining up to join IBM/Rational in porting their tools to Eclipse, a vibrant ecology of plug-ins, and an architecture designed explicitly to support extensibility and integration. Eclipse is more than just a development platform; it is a full life cycle platform.”»
  • Tool Will Connect Microsoft’s Visual Studio To Eclipse – Alexander Wolfe on 19 April 2005 reported, “A small, grass-roots development effort could presage better connections between Microsoft and the open-source community. Working in their free time, two Australian software developers are creating a software plug-in to tie Microsoft’s Visual Studio Team System into the open-source Eclipse environment. David Lemphers, a developer evangelist at Microsoft Australia, and Joe Sango, a senior developer at TeamForce, a software house in Victoria, Australia, last week set up shop on
  • Microsoft Gets ‘C’ for Effort at EclipseCon – Darry K Taft on 3 March 2005 reported, «In his keynote Thursday at EclipseCon, Lee Nackman, chief technology officer of IBM Rational Software, said part of the impetus for creating Eclipse was, “We decided we had to do whatever it would take to be competitive with Visual Studio on Windows.”»
  • Eclipse Con 2005: Visual Studio – Benjamin Booth on 3 March 2005 wrote, «The speaker was so well rehearsed it was unnatural … He spoke in trademark terminology and seldom referred to useful abstractions like “extension” or “plugin.” … moving smoothly into a lengthy overview of the various levels of the Microsoft VSIP program. I stopped listening intently and drifted into an acute awareness of the difference between Microsoft’s and Eclipse’s view towards developers. Microsoft wants your money while just wants your contribution.»
  • No Source Control Integration in Visual Studio 2005 “Express” Editions – Korby Parnell on 29 July 2004 wrote, “IMO, SCC is the concept every beginning developer should be forced to learn.” David further commented, “The main reason MS is putting out these Express products is to keep newcomer to flocking to free alternatives like Eclipse, right? Eclipse has CVS out of the box, so much for that.
  • Visual Studio .NET vs. Eclipse – Ryan Lowe on 27 October 2003 wrote, “Being mainly a Java/Eclipse developer I’m finding it quite hard to move to .NET/C# … Here’s the run-down on my issues: 1. C# is Java … 2. Refactoring … 3. Code Indenting … 4. Code Completion … 5. Code compiling … 6. Unit testing tool integration … 7. CVS integration …” The blog raise a number of interesting commentaries. A recent comment by Bolinfest on 27 January 2005 says, “So here it is, January 2005, and you know what? VS has the SAME problems that it did when this thread was started in 2003. Meanwhile, Eclipse has gone through a number of releases and its performance has improved (so those earlier comments about performance probably no longer hold true).
  • Eclipse Newsgroups – the window into the eclipse community.

About sabre23t

An analyst, researcher, civil engineer & information technologist working in a transportation company.
This entry was posted in Computers. Bookmark the permalink.

2 Responses to Eclipse, Visual Studio, NetBeans and WebSphere

  1. ashie says:

    hmm how well is Eclipse compare to IntelliJ IDEA?

    well in visual studio world you can have those missing feature but most certainly you have to pay for it 😉

  2. sabre23t. says:

    how well is Eclipse compare to IntelliJ IDEA?
    I think this IBM article Migrating to Eclipse: A developer’s guide to evaluating Eclipse vs. IntelliJ IDEA by David Gallardo on 8 September 2004 provides good comparison, ashie …

    Eclipse 3.0 and IntelliJ IDEA 4 have a number of important differences, but the most obvious difference is price: You must pay for a license to use IDEA, but Eclipse is free … many professional developers find that IDEA has all the features they need at a relatively attractive price. Nonetheless, while Eclipse doesn’t have all the features that IDEA does, the robust community that has developed around Eclipse has been quite thorough in providing the missing pieces in the form of third-party plug-ins.

    regards, sabre23t =^.^=

Comments are closed.