To view parent comment, click here.
To read all comments associated with this story, please click here.
"Java is slow" is a generalization, but unfortunately it is still almost always true today for end-user apps.
I haven't tried NetBeans 4.1, but the 3.X series was a dog. Woof, woof!
Eclipse has gotten to the point where there is so much Java mass, implosion has begun.
Even earlier versions of Eclipse will just die if you open too many files.
It is remarkable how much freedom from objectivity you get when you embrace free code. If Eclipse were judged as a commercial product, it would get slammed for crappy usability and performance.
Java would be a cool language if Sun truly optimized it for the desktop. Unfortunately, Java is optimized to sell Sun hardware. So everything runs slow and takes lots of memory -- as RAM is Sun's highest margin hardware offering.






Member since:
Hmmm I'm not so sure I would pin Java with the "performance sucks" montra anymore. I also use Netbeans 4.1 as well and it is very responsive. I have written many Swing apps and besides Netbeans use many others in my job everyday and they run just fine. RAD 6.0 and well Eclipse 3.1 are the only ones having a sluggish problem that I can see and it really revolves around their massive consumption of memory. I am not sure what the heck they are loading up in these tools in the background but holy cow they suck up a lot of RAM. Netbeans by comparison seems downright meager in its memory requirements. We have IBM Eclipse/WSAD/RAD 6.0 specialist's on staff and even with the performance tweaks they have recommended it still is slow as pond water.