4 ms·
A critical historical factor that doomed OS/2 from the outside was that following IBM tradition, after the evolution of PC -> XT -> AT, they told IT managers th
by hga 13y ago
A critical historical factor that doomed OS/2 from the outside was that following IBM tradition, after the evolution of PC -> XT -> AT, they told IT managers the PC-AT would be the last microcomputer they'd have to buy for a long time.
Unfortunately, per Bill Gates, its 286 was "brain dead chip" and absolutely hopeless and slow in Protected Mode, which is where it needed to run for a modern, large address space computer. As I understand it, the OS/2 inability to abandon the 286/PC-AT for the 386 is what really drove the split.
(It wasn't even IBM that came out with the first major 386 system, but Compaq.)
- rbanffy 13y agoThe 286 really had a lot of technical issues and IBM's apparent reluctance to embrace the 386 did hurt them in the long run (as well as MCA). Yet, for software built for OS/2, the 286 was just fine. Its main problem was dealing with DOS programs that wanted direct access to hardware. The fact that developing for OS/2 was painful and expensive was not helping. IBM made a lot of stupid decisions and Microsoft benefited greatly from those decisions.
- hga 13y agoReally? What I was told by various people who tried this is that Intel had no idea how people actually coded for the x86/weren't willing to make segment sizes larger than the original 64 KiB, and the penalty for loading a new segment register was "tens of cycles" per Wikipedia, I've heard on the order of 40 earlier. So a lot of existing code bases, including a couple I worked on for PCs (Gosling Emacs and a write once filesystem) ran, or would run, fantastically slower in Protected Mode. Yeah, sure, you could with no small amount of pain write more efficient code for OS/2 1.x, but why bother after Windows 3.x became a big hit? Oh, yeah, now you're reminding me that the cost to develop for it was $6K for the SDK in 2013 dollars, plus of course a PC-AT with a lot of memory (at least 1.5 MiB, which wasn't cheap back then, nor was the AT).
- yuhong 13y agoThe 32-bit OS/2 2.x and "NT OS/2" was a different story however, and while this decision was made before MS turned this project into a fiasco, this reminds me of how abandoning segmentation altogether and going for a flat address space for OS/2 2.0 and "NT OS/2" was a mistake for security reasons, and I realized that the Morris worm spread around Sept 1988, when both was in development (MS sent the first OS/2 2.0 SDKs to developers at the end of 1989).