4 ms·
My favorite is the MS OS/2 2.0 fiasco, which means most programmers were still stuck with programming for Win3.x long after the 286 became obsolete, while MS wa
by yuhong 13y ago
My favorite is the MS OS/2 2.0 fiasco, which means most programmers were still stuck with programming for Win3.x long after the 286 became obsolete, while MS was attacking OS/2 using unethical tactics. And don't forget DR-DOS too, as OS/2 never depended on DOS.
- hga 13y agoI watched that all at the time and it sure seemed to me that it was primarily IBM's fault, with Microsoft benefiting from it being so wedged. A lot of Microsoft's success in that era was due to its competitors simply dropping the ball while it executed at least minimally well. Now it's frequently executing poorly and in new markets its got some much more competent competitors ... and ones you can trust more. Yes, MS does have a very big problem here, I just don't see OS/2 as being a good example of it.
- yuhong 13y agoLook up "OS/2 Microsoft Munchkins" for one example of the unethical tactics I mentioned. And yes MS worked with IBM on OS/2 2.0 early on.
- seanmcdirmid 13y agoFun fact: I did an internship at IBM on OS/2 device drivers ('95, so Warp was out, Win 95 wasn't yet) in Boca Raton in offices that Microsoft had vacated just a few years earlier. Incidentally, That part of Boca was shutdown while I was there and moved to Austin; also I now work for Microsoft. Warp was really a nice system for its time. Switching to Win95 later was a huge step back for me.
- yuhong 13y agoAs I mentioned in my blog article, my favorite is how Caldera was able to sue MS based on Win95's continued dependence on DOS, which OS/2 never did.
- deleted 13y ago[deleted]