5 ms·
R&D funding provided by IBM wasn't classified as "profit". The Windows NT code base didn't use much from OS/2. In the end OS/2 was mostly worthless garbage to b
by nradov 2y ago
R&D funding provided by IBM wasn't classified as "profit". The Windows NT code base didn't use much from OS/2. In the end OS/2 was mostly worthless garbage to be thrown away; it had some good functionality in a few limited areas but was essentially a "local maximum" and had no viable path forward. If anyone wanted to turn OS/2 into a viable modern OS they would have had to start over from scratch.
- giamma 2y agoLink to a post I wrote some time back about OS/2 and some of its nice and unique features https://news.ycombinator.com/item?id=33107065#33119146 https://news.ycombinator.com/item?id=33107065#33119146
- Tor3 2y agoCan you be a bit more explicit in describing what the problems were? I don't immediately see why that wouldn't apply way more to Windows at the time. I did not use OS/2 much, but.. I did write some communication software so that we could work on a remote computer (this was via X.25, which was the option at the time for companies staying connected), and that was easy. Modern, I would say. Thread model easy to work with. I wrote a DMA driver as well. Again, a great API to work with, and overall a good experience. The user interface (GUI)? Any problems? A roadblock for the future? Can't really remember how it worked, but again - compared with Windows (even NT, which came about later), I can't recall anything "worthless garbage" with no path forward.
- nradov 2y agoThe most fundamental problem with OS/2 is that it wasn't designed as a multi-user OS from the start. It had some multi-user functionality but there were core architectural problems that made it impossible to move forward without a complete rewrite. On the UI side it also had a single input queue. Which was such a stupid design decision that I can't imagine what they were thinking. Fixing that would have also required a major rewrite.
- pavlov 2y agoIt sounds like the grandparent poster is maybe talking about OS/2 1.x, which was definitely hamstrung by 286 compatibility. But OS/2 2.0 was practically a 32-bit rewrite of the entire system with a new GUI too. It certainly was competitive with the first versions of Windows NT.
- cloudsec9 2y agoI'd disagree that OS/2 was "worthless garbage", as MS would keep using it for several generations for their server/LAN OS. I'd argue that OS/2 2.x was pretty much a ground-up re-write, as OS/2 1.x had been written for 16-bit 286 protected mode and not the 32-bit 386 protected mode which the next version targeted. IBM did insist that the new version run all of the 1.x 16 bit stuff, but like DOS and Win 3.x mode this was done through some virtualization if memory serves. The big hurdle OS/2 faced was being memory hungry at a time when memory prices were still high and when the installed base had less then half of the required amount by default.
- sydbarrett74 2y agoTo be fair, OS/2 could be run on less-beefy hardware that would've choked on NT 3.1.
- caspper69 2y agoIt wasn't just memory requirements that hurt OS/2. I'd argue one of the biggest hurdles was IBM couldn't stop being IBM for even one second to do any reflection on the realities in the PC market. They still thought they were going to have a renaissance with 386 PS/2 systems for goodness sakes. And man were they expensive. $195 for OS/2 2.0. That's about $434 in 2024 dollars, and the PS/2 systems that ran it best started north of $2k if memory serves. No one outside of corporate and the biggest enthusiasts were shelling out that kind of money for "a better DOS than DOS" (cough Desqview cough) or "a better Windows (3.1) than Windows (3.1)" (irrelevant and not that impressiive imho). Love them or hate them, Microsoft has always been good at hitting the 75th percentile, aka "good enough" and "cheap enough". They proved (conclusively) that customers will put up with a mountain of shit if you cost half of what your competitors do. Plus they knew how to make ISVs a lot of money too. IBM just couldn't get it's head out of it's ass, I mean the 1960s. And for the record, I salivated over OS/2. I scored a beta of 2.0 when I was 14 off of a BBS associate. I had an IBM laser printer, IBM typewriters, an original IBM PC. I thought back then that IBM meant quality (and to be fair, it did). But they didn't get it and Microsoft did. Windows 95 had pizzaz and hype, the CD had Weezer's Buddy Holly video (video!). They were working to get games running right under 95. They were courting all of the biggest application vendors. They were doing shit. IBM? Too busy being IBM.
- 20after4 2y agoOS/2 had true preemptive multitasking, which couldn't be matched on Windows systems until Windows 95. Far from worthless garbage, it was one of the only systems available that could do true multi-tasking on cheap PCs, at least until 95. I used OS/2 Warp to run a 2 node BBS on one PC in 94-95 time frame. The only other OS (that I'm aware of) which had that capability was DESQview¹ and that lacked any sort of GUI. 1. https://en.wikipedia.org/wiki/DESQview https://en.wikipedia.org/wiki/DESQview
- canucker2016 2y agoWindows NT 3.1 which shipped in July 1993 supported preemptive multitasking.
- dfawcus 2y agoThere were many available in that timescale. QNX DR Concurrent CPM which became Concurrent DOS DR FlexOS PC-MOS I seem to recall seeing a few others advertised in magazines at the time. As to DESQview, it had DESQview/X as an addition. As to unique bits, what OS/2 had was memory protection, but then so did QNX and FlexOS, I'm not sure about PC-MOS.
- t43562 2y agoIt was garbage while Microsoft was working on it. That NT wasn't garbage is due to it's being written by people from VMS who knew what they were doing. IMO.
- canucker2016 2y agoThe culture clash between IBM and Microsoft is evident from several postings by Raymond Chen: - https://devblogs.microsoft.com/oldnewthing/20220426-00/?p=106528 https://devblogs.microsoft.com/oldnewthing/20220426-00/?p=10... - https://devblogs.microsoft.com/oldnewthing/20240514-00/?p=109759 https://devblogs.microsoft.com/oldnewthing/20240514-00/?p=10... - https://devblogs.microsoft.com/oldnewthing/20240827-00/?p=110186 https://devblogs.microsoft.com/oldnewthing/20240827-00/?p=11...
- t43562 2y agoThat reminds me of when I briefly worked for IBM - an unpleasant corporate culture. I don't think it has anything to do with the end results, however. i.e. good people still ended up working for them. 1.2 was problematic and 2.0 worked. 1.2 was Microsoft and 2.0 was IBM. From what I have read the NT team didn't want any of the MS OS/2 developers - this is just memory - and it was related to perceived code quality or something like that.