Sponsored Link •
It always seems that developers are more willing to agree on music, one of the most diverse forms of self-expression available, than they are to agree on their development environments
Its all been said before but I have never seen as much fanaticism in the development world (well apart from the My language is better than yours arguments) than in the land of IDEs.
My current poison I dont say favourite is Eclipse 3.0 M8. It does what I want it to, and Im happy with it, it has faults, show me an IDE that hasnt.Sometimes it's slow as hell, but sometimes so am I.
The important thing is that Ive learnt to understand these faults, and get around them. This is not to say that Ive not used other IDEs IntelliJ IDEA, JBuilder (from back when it was still half Delphi!), Netbeans, JDevloper, VAJ, Visual Café (then again you could say that Ive missed out on a whole load of other IDEs like Kawa, and Emacs/JDE (Yes I do consider anything that makes the general development environment more integrated, an IDE).
Before I get inundated with Why didnt you stick with [whichever]? posts, the only other IDE that I got on with, was IDEA, but because I couldnt see multiple project trees at once without opening multiple windows, I moved to Eclipse. But this being said, many of these IDEs have great features that are to be praised, from IDEAs almost total embrace of refactoring as a Good Thing that developers actually want, to JBuilders two-way, non-invasive, visual development (some might call constantly having a jbinit() method as invasive Im not one of them); from Netbeans build on plugins philosophy to JDevelopers visual support for Struts.
Competition is good, but familiarity breeds contempt. Many developers advocate their own IDE whilst both disparaging the choices of others, and ignoring the failings of their own environments. Sadly, this scenario can be applied to many more things than just IDEs.
We do it with frameworks, Persistency solutions, etc, etc.
I think in many ways it is this blind loyalty to one particular brand (and not just IDEs) and futile infighting that could harm Java. And its not just infighting between developers, there are the Open Source and Dont Open Source camps, and the JCP cant even agree because theyve all got their own agenda see JSR 243 JDO 2.0
Just because your problem domain fits well with one particular problem dont just assume that it will fit everyones, discuss it properly and objectively.
As the Beatles song goes, But though they may be parted, there is still a chance that they will see, there will be an answer, let it be.
There doesnt have to be one answer, just dont assume that everyone will find the same answer as you, moreover, dont think that everyone is inferior because they have a different answer to you.
|Calum Shaw-Mackay is an architect on Java and Jini systems, working in the UK. His interests lie in distributed computing, adaptability, and abstraction. Calum has been using Jini for longer than he would care to mention. His main area for taking the blame (some people would call it 'expertise') is systems integration and distributed frameworks, and is an advocate of using Jini's unique strengths to build adaptable enterprise systems. His opinions are his own. He's tried to get other people to take his opinions off him, but they just won't.|