3 ms·
When I first started at Microsoft, I once told a coworker something like, "Hey, I've heard NT revolutionarily elegant, but so far, I've just seen features that,
by quotemstr 14y ago
When I first started at Microsoft, I once told a coworker something like, "Hey, I've heard NT revolutionarily elegant, but so far, I've just seen features that, while fairly nicely implemented, are universal across operating systems." He replied by reminding me that other operating systems have caught up, while NT was pretty close to its present design even in the early 90s --- it was like a modern operating system had travelled through time back to 1992. It was revolutionary.
(I spoke to someone else who was utterly amazed that NT allowed driver development without requiring that the whole kernel be relinked from object files.)
- slacka 14y ago> In the time since that comment was written (just under 5 years), Linux replaced most graphics drivers with ones based on in-kernel modesetting and the DRI2 interface. This was done without breaking applications. So, the assertion that changing the video driver model would be disruptive is kind of disproven by reality. mjg59, I could not disagree more. Without working drivers what good are working apps? I can run my Radeon x1900 under Windows 7/8 with Windows Vista drivers. Runs StarCraft2 and newer FPS games just fine. The Linux kernel devs are so determined to break binary compatibility, I haven't been able to run with ATI's proprietary binary drivers for years. While AMD was a good open source citizen and released the specs, the open source drivers for my card are useless for anything other than 2D. That's about as disruptive as it gets.
- hga 14y ago"The Linux kernel devs are so determined to break binary compatibility...." Well, of course. As long as no one else can use their drivers, they won't get a serious competitor in open source land. Pity about the rot in official drivers, though (e.g. for me, the latest is USB 1.x sound dongles in debian lenny -> squeeze). Which suggests to me that if I wanted to write a OS that could become really popular I should use Windows device drivers in a microkernel approach where each lives in its own address space and process. Hmmm.
- blinkingled 14y ago>other operating systems have caught up, while NT was pretty close to its present design even in the early 90s The one thing you will find almost as a theme with Linux design is that there is minimum of "future" it. That applies to most of the Linux user space as well. This is a good thing and a bad thing. For example multi-gpu systems with multiple outputs were not taken into consideration when both the Kernel and Xorg parts were designed. They took the most common usecase of single GPU, probably made some assumptions around it and coded something that works for that usecase. Microsoft, on the other hand (almost out of necessity) had to actually design the NT Kernel while making no assumptions - multi GPUs may not have existed when XP was released but none the less MS had to design for the eventual reality when some OEM will stuff 2 GPUs and will have to write drivers for it without Microsoft being able to change the XP kernel design or even implementation in any way. I am sure the same can be said about scalability - when massively multicore CPUs weren't around NT kernel was mostly up for task of supporting them, whereas Linux adopted with lot of scalability related work that followed after the fact. (Remember the early NT vs Linux benchmarks?) Designing for future is bad because it comes with certain baggage and to an extent added upfront costs. It is good for future compatibility, code maturity and obviously saves rewrite efforts - you don't have to rip off all the code and start over and take care not to break existing software etc. There is less code churn in Windows world I am sure than there is in the Linux world where people are constantly adopting to new realities. This creates an environment ripe for new bugs, instability and only with the amount of volunteer effort the cost factor can be lesser than prohibitively expensive.
- pjmlp 14y ago> The one thing you will find almost as a theme with Linux design is that there is minimum of "future" it. That applies to most of the Linux user space as well. This is a good thing and a bad thing. Maybe because it is mostly about the "past", bringing enterprise UNIX and mainframe designs into Linux?
- blinkingled 14y agoThat applies for the core kernel. But drivers/hardware support on the other hand is pure Linux way of doing - don't think any mainframes or enterprise UNIXes had to bother with multi-GPU systems, so what you see in that area of Linux design is pure, quick to market hackery aided by delay-design-until-it-no-longer-works-without-it. It's depressing in a way but that's the best we got when it comes to a hackable Open Source OS that you can somehow run on your hardware and even patch things you don't like.
- lolcraft 14y agoIDK, from what I've just read NT looks like someone took Minix (released in 1992) and worked on it to make it useful. Plus adding a subsystem layer. Frankly, I'm still more impressed by a monolithic kernel that did it better, before: Plan 9 (released in 1991). What use is for NT to be object-oriented, if it can't share its objects through a network like Plan?
- pjmlp 14y ago> IDK, from what I've just read NT looks like someone took Minix (released in 1992) and worked on it to make it useful. Plus adding a subsystem layer. VMS. > Frankly, I'm still more impressed by a monolithic kernel that did it better, before: Plan 9 (released in 1991). What use is for NT to be object-oriented, if it can't share its objects through a network like Plan? Sadly the UNIX crowd decided it was not worth it adopting it.
- eschaton 14y agoMinix wasn't released in 1992, the first version was from 1987.
- binarycrusader 14y agoI don't think you were implying that all other operating systems were catching up, just most of them. For example, Solaris has had a stable driver DDI (Device Driver Interface) for years. This is what allowed ISVs to write drivers for ancient versions of Solaris that still work today (assuming the base hardware platform is still supported). That's also what allows the latest versions of the nVidia driver to generally just work on different releases of Solaris.