5 ms·
Are there any old-schoolers around here who remember IBM's OS/2 and how it could have changed the PC world completely http://en.wikipedia.org/wiki/OS/2 http://
by ck2 14y ago
Are there any old-schoolers around here who remember IBM's OS/2 and how it could have changed the PC world completely
http://en.wikipedia.org/wiki/OS/2 http://en.wikipedia.org/wiki/OS/2
Its design was supposedly far better than NT
(it initially came on 50 5.25" disks, that was "fun" to install)
I think UPS was the largest user/developer.
You know the company Parallels that made Virtuozzo (and OpenVZ) - well it was initially formed to make virtual environments to run OS/2.
- pjmlp 14y agoSure! At the kernel level API it wasn't much different than Win32. I bet if OS/2 had gotten a better future, nowadays we would see rants about it similar to Win32. The SOM C++ API was quite interesting, a Smalltalk metaclass like system for C++. Another nice thing was the Visual Age for C++ provided an image like environment for C++, which made compilations quite fast.
- quotemstr 14y agoImage like? Like Emacs unexec?
- pjmlp 14y agoLike Smalltalk and Lisp Machines, well kind of. I never used, just read about it in DrDobbs back in the day. If memory serves me right, it imported the C++ code into a database and the editor was able to manipulate the code AST directly, but it consumed lots of memory, both RAM and disk space. Maybe someone with more knowledge can fill the gaps.
- pavlov 14y agoActually NT was originally supposed to be marketed as OS/2 3.0. The OS/2 project was a collaboration by Microsoft and IBM. Sometime around 1989-90, the latter was in charge of OS/2 2.0 while Microsoft was working on the next generation. The unexpected success of Windows 3.0 made Microsoft see they could do it on their own without IBM, so NT became the next generation of Windows instead. IBM's OS/2 2.0-4.0 was a competent 32-bit OS for its era, but NT's design was more modern. The only thing OS/2 had going for it was a smaller footprint (it could run on 8-16MB of RAM while NT practically required 32MB) and a more innovative user interface, but this advantage was basically eliminated when Microsoft ported the superior Win95 UI to NT.
- huhtenberg 14y agoFor what it's worth I remember a distinct feeling of being really frustrated with Warp's GUI. I don't remember the specifics, but one thing stuck out - it didn't have something as simple as "arrange desktop icons on the grid", so you'd end up with this mess on a desktop. The GUI might've been innovative, but it was inferior to Windows 95 and IBM didn't seem to care about that.
- cturner 14y agoAs I remember it - you'd put your icons about where you wanted them, but they wouldn't be aligned pixel perfect. So you'd right click and see "arrange desktop icons on the grid" and think that must be it. But that would rearrange everything starting at the top left, like modern Windows does. i.e. Rather than doing what you needed, it would destroy ten minutes of painstaking layout. There was no way to do the assisted alignment you actually wanted. They'd pitched a fabulous, malleable, document-centric desktop. Technically it was all there. They didn't quite get it to the user. People who were fluent in C could probably have done some quick fixes and made it hum. I think this was in version 2.0, and I watched it go unfixed in 2.1, warp. Can't remember if it was broken in 4, think so. Good example of the way OS/2 dev focused on ticking feature checkboxes (3d icons! a different dock! obscure mainframe compatibility features that mainstream users will never care about!) not users.
- Osiris 14y agoShadow's were pretty cool. It was a pointer to an original object (since the GUI was object oriented). If you deleted the original item, all the shadow's disappeared also. Microsoft implemented "Shortcuts", but those were files that pointed to another file, so deleting the original file just left around broken shortcuts. You could also use the Font panel to drop fonts into any application and it would change the UI font. Some apps actually saved that as a preference and remembered it on next startup but others didn't. I got eComStation running in a VM a while back and I realized that my nostalgia for OS/2 didn't quite match the reality.
- ksk 14y agoDon't recall the initial versions, the only one I used was OS2/Warp in August '95 and it was awesome ! (IIRC it came on a CD)
- ics 14y agoI seem to remember having OS/2 on a few computers at school (K-8) for some reason, but those were the days that most were running Win95 and there were just a couple Macs that nobody knew what to do with (I eventually got permission from the IT team to "set them up", which was basically just feeding floppies and pressing okay). I think the MTA (in NYC) still uses it to process subway fares...
- captaincrowbar 14y agoI did a lot of development on OS/2 applications in the mid 90s, mostly on the Warp 3.0 version. Eventually we switched to Windows NT4 once it became clear that OS/2 had had its fifteen minutes. I quite liked it at the time, but to be honest I think the wistful "could have changed the PC world completely" stuff I sometimes hear is just rose tinted nostalgia. It was a very good OS for its time; its main competition then was Windows 95, and there was certainly no contest there. But the NT kernel was a different matter, especially after it got a saner UI in NT4. There were no huge advantages to one or the other there (with one exception, see below). Compared to very different modern OSes such as OSX or Linux, OS/2 and NT4 were close siblings. OS/2's one real Achilles heel, which gave us endless trouble, was the synchronous input queue, shared by all programs that had a GUI (including the OS desktop). The upshot of this was that, if a user-facing program crashed, it was very likely to freeze up the OS and require a hard reboot. When we switched to NT4, the vast improvement in reliable uptime was a breath of fresh air (if nothing to write home about by modern standards). I gather they partially fixed this in OS/2 4.0, but by then the writing was on the wall. OS/2 faded away before the rise of modern malware had really hit its stride, but I suspect the SIQ problem would also have led to all sorts of security issues. For example, look up "shatter attack"; that was bad enough on Windows, but I'm pretty sure OS/2 would have been even more vulnerable to that sort of technique. While I certainly wouldn't claim that son-of-NT's victory over OS/2 had anything to do with its technical merits, I do think that, at least between those two lines of development, the (slightly) better OS won.
- pavlov 14y agoOS/2's one real Achilles heel, which gave us endless trouble, was the synchronous input queue So there was basically one global event loop for the entire OS? Interesting. I can see how that would make the window system a lot simpler to write -- not unlike the reasons why Node.js and other evented web frameworks have become popular. At the same time it is, as you mention, an approach that would have been doomed to fail spectacularly by the late '90s when it became commonplace for desktop OSs to run unverified code downloaded from the Internet...
- quotemstr 14y agoAh, so in OS/2, it's as if every program called AttachThreadInput on every other thread? Why was it designed that way in the first place?
- bdunbar 14y agoMy boss was huge into OS/2 at the time. He got it up, and running, at home, and work. Reported (and I recall agreeing after playing with it) that it was a better environment to run windows / DOS applications than was Windows. Our employer (the US Marines) was not officially interested in the idea ... and so the idea never went past that.
- ams6110 14y agoI think "a better Windows than Windows" was an official IBM marketing line for OS/2 for a while. I used it for a while in the early 1990s as a contractor in an "IBM shop". Literally everything they bought was IBM. From the mainframe to Terminals, printers, PCs, OSes. I remember it being painfully slow.... but the PS/2 PC it was running on was probably underpowered (as is typical, contractors got the oldest hand-me-down workstations).