🚀 go-pugleaf

Let me start off by saying that I've always really liked Borland products (I
never like Symantec) -- but is it just me or does anyone else running
JBuilder with BAS4.5 wish they could go out and buy a 50GHz machine just so
JBuilder runs as fast as any typical native Windows app of today ?

For cryin' out loud, why build the GUI in Java, write the damn thing in C++
and Assembler instead, and I guarantee that no one will ever buy a
competitors's Java IDE, at least not for the foreseeable future.  Showcase
java at what it's good at, EJB, network apps, etc, but don't build GUI's
like this in Java any more!!

Assuming, the aforementioned suggestion is ignored, is there any way to make
speed up JBuilder - maybe make it a little more responsive?  I like the
product big time, but I think Swing could stand an optimization or
two...it's sickening to be able to see every little screen repaint in clear
detail (or having to wait 4 seconds after a mouse click for something to
happen) while right next to it, similar IDE's systems like Visual C++ are
just smokin' along-side it