4 ms·
The same happened to VisualAge for Smalltalk where in 2005 Instantiations, Inc. took over "worldwide rights for this product" - and is still offering it...
by pulse7 5y ago
The same happened to VisualAge for Smalltalk where in 2005 Instantiations, Inc. took over "worldwide rights for this product" - and is still offering it...
- kencausey 5y agoI kind of wish that VisualAge for Java was still a thing but in reality it is unlikely that I would do anything more with it than I ever did with v1.0 and v2.0 which still sit on a shelf.
- pulse7 5y agoThe 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 agoYes, 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.