3 ms·

The NT kernel was actually an IBM project, which got divorced from IBM because of contract stuff and Microsoft got to keep a copy. It grew out of VMS which was

by inigyou 3mo ago

The NT kernel was actually an IBM project, which got divorced from IBM because of contract stuff and Microsoft got to keep a copy. It grew out of VMS which was a heavyweight OS for DEC VAXen, which IBM acquired.

foobiekr 3mo ago
No. You are thinking of the ibm Mach-kernel “workplace OS” which descended from the os/2 interaction once IBM and Microsoft broke up. NT was entirely a Microsoft project. They hired the prism team from DEC and started completely from scratch. Mach and microkernels were hot at one point despite having many issues with performance.
fryanyway_swe 3mo ago
Well, somewhat. It has been a while since I read a book on NT kernel - "Showstopper!: The Breakneck Race to Create Windows NT and the Next Generation at Microsoft" NT kernel was "supposed" to run OS/2 apps and Windows apps. But the NT kernel is of MS making, NOT IBM. The connection to VAX/VMS is due to MS hiring Dave Cutler, who worked there before. https://en.wikipedia.org/wiki/Dave_Cutler https://en.wikipedia.org/wiki/Dave_Cutler
- deleted 3mo ago
  [deleted]
- daemin 3mo ago
  If you want to read that book I would try and find a second hand copy of the original print. I bought a more recent print from Amazon and it seemed like it was a non-edited OCR'd scan of the original, plenty of words that should have been other similar words, paragraph/page breaks in the middle of pages, and other irregularities. I enjoyed reading it but would burn this version of the book if I ever got a copy of an original print.
wvenable 3mo ago
That is not correct at all. Part of the revisionist history these days is making IBM out the be hero that was crushed by Microsoft but nothing could be further from the truth. IBM was the lumbering giant that evaluated developers by lines of code produced, had 14 levels of management, and wanted to protect their hardware interests more than anything. Microsoft hated working with them because they sucked. OS/2 was so buggy that the first patch was almost as big as the entire original install.

by inigyou 3mo ago

foobiekr 3mo ago

No. You are thinking of the ibm Mach-kernel “workplace OS” which descended from the os/2 interaction once IBM and Microsoft broke up. NT was entirely a Microsoft project. They hired the prism team from DEC and started completely from scratch. Mach and microkernels were hot at one point despite having many issues with performance.

fryanyway_swe 3mo ago

Well, somewhat. It has been a while since I read a book on NT kernel - "Showstopper!: The Breakneck Race to Create Windows NT and the Next Generation at Microsoft" NT kernel was "supposed" to run OS/2 apps and Windows apps. But the NT kernel is of MS making, NOT IBM. The connection to VAX/VMS is due to MS hiring Dave Cutler, who worked there before. https://en.wikipedia.org/wiki/Dave_Cutler https://en.wikipedia.org/wiki/Dave_Cutler

deleted 3mo ago
[deleted]
daemin 3mo ago
If you want to read that book I would try and find a second hand copy of the original print. I bought a more recent print from Amazon and it seemed like it was a non-edited OCR'd scan of the original, plenty of words that should have been other similar words, paragraph/page breaks in the middle of pages, and other irregularities. I enjoyed reading it but would burn this version of the book if I ever got a copy of an original print.

wvenable 3mo ago

That is not correct at all. Part of the revisionist history these days is making IBM out the be hero that was crushed by Microsoft but nothing could be further from the truth. IBM was the lumbering giant that evaluated developers by lines of code produced, had 14 levels of management, and wanted to protect their hardware interests more than anything. Microsoft hated working with them because they sucked. OS/2 was so buggy that the first patch was almost as big as the entire original install.