4 ms·
In the case of Microsoft they directly acquired the original DOS and the designers of Windows NT - so they've perhaps done that twice?
by arethuza 8y ago
In the case of Microsoft they directly acquired the original DOS and the designers of Windows NT - so they've perhaps done that twice?
- samstave 8y agoI didnt know this about NT - Where did they come from?
- deleted 8y ago[deleted]
- Jtsummers 8y agoNT has a lot of VMS roots.
- arethuza 8y agoProbably a coincidence, but a lot of noticed that "WNT" is one letter on from "VMS". Mind you, HAL is one letter behind IBM.
- deelowe 8y agoSome claim the HAL/IBM connection was intentional (though Stanley denies it).
- deleted 8y ago[deleted]
- andyjohnson0 8y agoCoincidentally HAL is also Hardware Abstraction Layer, part of the WinNT kernel's architecture. https://en.m.wikipedia.org/wiki/Hardware_abstraction#Microsoft_Windows https://en.m.wikipedia.org/wiki/Hardware_abstraction#Microso...
- barkingcat 8y agoDave Cutler and his team of OS designers from DEC integrated with Microsoft software engineers to create the NT kernel. Cutler was a crucial figure in DEC, but was waysided by management so he jumped ship, and built the design he wanted to build at DEC (but never got management buy-in for) at Microsoft. All outlined in the book Show Stopper! THE BREAKNECK RACE TO CREATE WINDOWS NT AND THE NEXT GENERATION AT MICROSOFT Also, if you took a peek at his wikipedia entry, the guy is behind almost every large MSFT OS related initiative in the last few decades: NT, Azure, XBox hypervisor. https://en.wikipedia.org/wiki/Dave_Cutler#Microsoft_(1988_to_Present) https://en.wikipedia.org/wiki/Dave_Cutler#Microsoft_(1988_to...
- simonebrunozzi 8y agoAnd if I remember correctly, NT's kernel was a microkernel. It seemed to be the best choice for the future, back then.
- DaiPlusPlus 8y agoWindows NT was a hybrid: the graphics and windowing system is in the kernel for performance reasons (try running X on commodity hardware in the early 1990s) whereas Windows CE was all microkernel.
- StillBored 8y agoI wish people would stop saying its a hybrid because of the graphics being moved into the kernel... That doesn't make it a hybrid anymore than having the filesystem in supervisor/kernel space does. Its a hybrid because its designed/layered like a micro-kernel with the individual subsystems appearing to do message passing and using subsystem managers (I/O manager, process manager, object manager, etc) which monitor/etc the message flows. Yet, instead of doing context/privileged switches when it passes messages/IRP's it simply makes abstracted function calls which hand ownership of the message to other subsystems that exist in the kernel's address space. This means you get a most of the abstraction/stability effect of having a micro-kernel without paying the context switch and message copy penalty. NT has a crazy awesome design, which is somewhat obscured these days, but has yet to really be surpassed by anyone (IMHO).
- codetrotter 8y agoYou can read more about it in a story from 1998 that was posted here two days ago (probably part of the reason that so many ITT know the story ;)) https://news.ycombinator.com/item?id=17652502 https://news.ycombinator.com/item?id=17652502
- cjarrett 8y agoShow Stopper! is a great read. My copy is always lent around the office, especially to interns: https://www.goodreads.com/book/show/1416925.Show_Stopper_ https://www.goodreads.com/book/show/1416925.Show_Stopper_