3 ms·

The main problem with VisualAge for Java was that you couldn't integrate external libraries easily... it was not file-system-based, like IDEA/Eclipse are today.

• kencausey 5y ago
  Yes, as I tried to imply, I never really used it enough to feel the pain of it's idiosyncratic implementation. Before I even posted the earlier comment I checked Wikipedia about VisualAge (to ensure I hadn't missed later releases) and learned, I think for the first time, that VisualAge Java was apparently implemented by extending a Smalltalk VM and presumably used the standard Smalltalk image model. I have been a Smalltalk aficionado and see some value in the image based model and think I might not feel the pain as much as the average user.