Live data from Hacker News

Half an operating system: The triumph and tragedy of OS/2

arstechnica.com

121–130 of 191 posts

Re: Half an operating system: The triumph and tragedy of OS/2

#121
post #52

Earlier quoted context omitted.

I think it's a bit more complicated than that. Put yourself in the shoes of someone who'd grown up on mainframes. The systems you're used to are fabulously expensive, sure, but their operating systems have sophisticated architectures that allow them to easily juggle multiple users running multiple programs while maintaining the security of the system overall. They are the completest expression ever realized of forty…

Regarding vulnerabilities, which many think (wrongly) are not present in mainframes, because they are networked nearly as much, and have massively fewer programs running on them, don't show up as much. But they are there.

Certainly, but it's also worth noting that the environments in which programs execute on most mainframes are much more restricted than those of even the typical servers of today, and have been by default for decades.

Re: Half an operating system: The triumph and tragedy of OS/2

#122

Earlier quoted context omitted.

Yeah, the Amiga seems like it completely dominated the multimedia niche, but the multimedia niche of the time essentially consisted of the demoscene. Which was great, except that the demoscene was not that large.

Huh, Amiga (1000 onwards) was big in video. Especially smaller TV stations that couldn't afford SGIs. Amiga (and SGIs) were light years ahead of Macs in graphics. People often forget this fact.

Amiga 2000 (mostly) + NewTek Video Toaster[1] were the driving force behind the TV graphics back then.

[1] http://en.wikipedia.org/wiki/Video_Toaster

Re: Half an operating system: The triumph and tragedy of OS/2

#123
post #41

Earlier quoted context omitted.

My computer had 8mb RAM at the time and NT required 16 to install so I "borrowed" another 8 from one of the school computers, installed NT and then returned the memory. It ran well enough on 8.

I was lucky enough to have a 486DX-50 (not a DX2-66)with 16 MB of RAM, so it ran perfectly for me. Even with what was bleeding edge hardware at the time, I still remember trying to finish writing my senior project using Corel Draw and Microsoft Word on Windows 3.11, and having my computer crash ever 30-45 mins, and my project partner eventually broke down and started crying because of how frustrating it was.

If you ever work with an older person who reflexively saves a document every few minutes, you know why.... habits established back when crashes were frequent and sadly, accepted.

Re: Half an operating system: The triumph and tragedy of OS/2

#124

I bought OS/2 for work to run on some DEC PC (not the damn Rainbow, the decent 486 DEC sold). The graphic card (S3) wasn't supported out of the box, so I called the IBM and got nowhere other than an acknowledgement it existed. I called DEC and they too believed it existed, so they (while I was still on the line) called their contact at IBM. After being transferred twice, we arrived at the person who could mail me the…

> not the damn Rainbow

Hey I had a Rainbow! It was pretty amazing IF it had it's full potential it would have been the best computer until the Amiga came out.

Rainbow: CPUs - Z80 (8 Bit) and a Intel 8080 OS - CP/M and MS-DOS Could be upgraded to 286 later.

Would have been perfect BUT they didn't get things setup correctly and I was really stuck in Z80 CP/M land.

Re: Half an operating system: The triumph and tragedy of OS/2

#125
post #6

If anyone wants an insider's view, here's a Usenet post from one of the early Microsoft employees, Gordon Letwin: http://gunkies.org/wiki/Gordon_Letwin_OS/2_usenet_post Somewhere in the Usenet archive is Gordon trolling the OS/2 users for weeks (or months?) on end. I can't remember the exact details, but he had a bet with several people that Windows would have multitasking, or that OS/2 wouldn't have some sort of mul…

So, did Letwin ever pay up?

I think Letwin turned out to be right. I can't find the Usenet thread. It was from the early 1990's.

Re: Half an operating system: The triumph and tragedy of OS/2

#127
post #112
post #65

Earlier quoted context omitted.

Yes, many like to bash Windows, but the NT family is actually a VMS at heart, spoiled by a not so good user land experience. I once attend a session by him about the Windows kernel design, quite interesting.

VMS + 1 = WNT, in the same way as IBM - 1 = HAL. (So far as I know, both of these are just amusing coincidences.)

In the 2001 audio book Arthur C Clarke had a 15 minute intro where in it (amung other things) he explicitly says it is a coincidences and lists the page in the book explaining what HAL stands for.

Re: Half an operating system: The triumph and tragedy of OS/2

#128

> Long before operating systems got exciting names based on giant cats and towns in California named after dogs, most of their names were pretty boring. Ah, yes. Mavericks, California. It's a great little offshore town, just off Pillar Point. I love that town. Kidding aside, this is a great article. Related to this story, the Windows 3.0 visual shell was originally not supposed to be Program Manager and File Manager.…

I knew about Alan Cooper legacy in VB, but not the Ruby project. Is VB the only program that used this idea at Microsoft ? even another internal project ?

Were you from tripod too ?

Re: Half an operating system: The triumph and tragedy of OS/2

#129

Earlier quoted context omitted.

The photo should be in a National Geographic captioned "A Unix beard in his natural habitat".

In its natural habitat. A Unix beard is genderless; it merely seems to exhibit a preference for male hosts.

I thought Unix greybeards were like Tolkien's dwarves in exhibiting little sex-based dimorphism.

Re: Half an operating system: The triumph and tragedy of OS/2

#130
post #4

Great read. In the end, it seems like a classic failure to resolve the innovator's dilemma. IBM decided that the future of computing would revolve around mainframes because they liked mainframes , not because that's where the facts led them. And ultimately they paid the price for it.

It also rings to me as a story about artificial limitations. They were scared another program could do more for less. IBM is doing good today I think, I wonder if they'd fare better going the Apple/Google 'making people's live better' myth/motto, even at the ~sacrifice of their traditional comfort zone / cash cow.
Post reply on HN