Item — HN Reader

As a developer using OS/2 in its heydey and the early part of its decline I would say your assessment was spot on. Before NT the pre-emptive multi-tasking and ability to run Windows executables as well as OS/2 ones was a significant merit. Once NT came along it so clearly didn't have a future.

By the by "IBM VisualAge for C++ for OS/2" has to be a contender for world's least snappy product name.

3 comments

As a former IBMer in '90s, I would like to nominate VisualAge for Java as another example of awkward naming choices. The team I was on used VAJ (as it was always referred to in electronic communications) extensively. In speech, people would often pronounce the acronym rather than say "VisualAge" or "VisualAge for Java". Of course, they pronounced it "vadge", because how else would you pronounce VAJ? Sometimes it was said by someone being mischievous, but much more often it was said by people who had no idea that it was slang for something much more exciting.

Brilliant. Thanks for this! I loved OS/2 when I used it briefly, but my computer wasn't powerful enough to run the OS let alone making any dev environment run. IBM should have shipped their Dev environment with OS/2, and then it might have caught on as it then would have had a very low barrier to entry.

Couldn't agree more re: product names. What people would call Sushi, IBM would specifically call "dead raw cold fish on white rice".

I still twitch a bit over the WebSphere branding apocalypse when they decided their (IMO ghastly) Java app server's name should be applied to All The Things.

That sounds terrible. One positive, potentially, that I found was an object-based GUI or system model that supposedly let the developers handle that stuff better than Windows or UNIX/X-Windows. OS/2 fanboys always say something about it. Any insight or opinions on that?

Nope, I'm afraid I was using the Visual Age class library (which was pretty good) for most if not all of the development work I had a hand in.