 |
JBuilder
Why I love JBuilder:
===============
It is fast.
It has a lot of refactoring support.
It has good source control integration.
It has a lot of wizards that generate all the tedious, declarative stuff that most enterprise specifications require.
I plug in BeanShell and write my own macros and scripts to make it do all kinds of cool things with the OpenTools api.
It is fast for projects with more than 6000 files.
It has great support for using jUnit to run and debug either whole sets of tests or individual tests.
The integrated OptimizeIt? support makes it easy to make my apps faster.
I can turn my project into Ant files lickity-split.
Borland has always rocked and keeps on rocking.
Why I hate JBuilder:
===============
It costs a pretty penny (> $3000 for the enterprise edition).
Its user interface creator is only usefull for programmers in that you have no idea how to use it unless you know the API for the widgets and layout managers. Limiting its use quite a lot.
They dropped Mac OS X (just because Apple's MRJ was a little late to market).
CVS/VSS integration is laughable.
???Funny, I think they have a great CVS support. I have forgotten all the cvs command by now. It was a shame that CVS support was only in Enterprise SKU, but that has changed, along with a lot of other cool features.
Actually; when the project (file) itself was changed by someone else it is not used by JBuilder after an CVS update. This is a very critical bug IMO.
Updating project file happens once a year in my project. And when it happens, I just need to restart JBuilder. So this is not a "very critical bug" IMO.
If other project team members update a JAR (e.g. for EJBs), one has to exit JBuilder in order to replace the JAR on your system.
Discussion about JBuilder
This article needs to be rewritten to read more like an encyclopedia entry rather than one person's POV. Also, JBuilder X Developer supports Mac OS X 10.2. -- Main.redwolf - 07 Jun 2004
|