7 ms·
I thought the big reason for moving the GUI into the kernel was for performance rather than compatibility.
by wvenable 12y ago
I thought the big reason for moving the GUI into the kernel was for performance rather than compatibility.
- CurtHagenlocher 12y agoThat is correct.
- 2510c39011c5 12y agoin terms of GUI, performance is responsiveness... and for a windows system, it needs to support a range of hardware configurations...Some could be really slow...
- Animats 12y agoThat was the official word from Microsoft at the time, but Mark Russinovich, who had Sysinternals.com at the time, benchmarked and said that pushing low-level graphics commands (draw line, fill, etc; stuff graphics cards do) across the kernel boundary wasn't a bottleneck. He was critical of those decisions. Microsoft eventually hired him to shut him up.
- jen729w 12y agoAnd because he was clearly a genius.
- Animats 12y agoThere's a story behind that buyout. Russinovich had a business called Winternals, and had written NTFSDOS [1], which allowed access to NT file systems under DOS.[2] Microsoft didn't like that, because it allowed booting from a floppy, bypassing NT's security restrictions, and resetting the administrator password, copying, or modifying files. (The concept that a computer could be secure when someone had enough physical access to boot a new OS seems silly now, but back then, the opposition was script kiddies, not intelligence agencies and organized crime.) So Microsoft bought Russinovich out. Wikipedia: "Winternals was acquired by Microsoft mid-2006. Microsoft has removed any traces of NTFSDOS..." [1] https://en.wikipedia.org/wiki/NTFSDOS https://en.wikipedia.org/wiki/NTFSDOS [2] https://web.archive.org/web/20000126093942/http://sysinternals.com/ntfspro.htm https://web.archive.org/web/20000126093942/http://sysinterna...
- asveikau 12y ago> Microsoft didn't like that, because it allowed booting from a floppy, bypassing NT's security restrictions, and resetting the administrator password, copying, or modifying files. This sounds nonsensical, like folk history. You can already create a boot disk to do this using all Microsoft tools: Assuming the volume is not BitLocker'd it's pretty simple to do all of this stuff with WinPE [1], including the version that shipped in 2006, or with a Windows setup DVD. Or you could simply move the drive to a machine where you are an admin. I am pretty sure they bought winternals because they wanted to hire MarkRuss. [1] http://en.wikipedia.org/wiki/Windows_Preinstallation_Environment http://en.wikipedia.org/wiki/Windows_Preinstallation_Environ...
- toyg 12y agoNTFSDOS was released in the late '90s, Microsoft acquihired Russinovich in 2006. That program wasn't any more of a factor than all the other wonderful utilities he'd developed over the years. In fact, if you're looking for something Russinovich was forced to retire right after acquisition, you really should mention NewSID.exe, which was really shut down hard while in ascendance (as virtualization became commonplace). I think MS just wanted to hire one of the best Windows hackers of all time, and they pounced as soon as they got a window of opportunity for whatever reason. Everything else was a bonus.
- 72deluxe 12y agoYes, Mark was running sysinternals for years before Microsoft hired him. Great programs he produced though! Really really helpful. One of the first things I install on a new OS.
- nbevans 12y agoGod you don't half speak some utter shit. This backward compatibility crusade you are on is hilarious. Please consider that Windows NT+ developers have never been required to use a publicly exposed API that requires calling into the kernel to draw lines and scrollbars. Those APIs have always been in the from of DLLs on the user-mode side of the OS, e.g. User32.dll, Gdi32.dll etc etc. This is how Win32 API has always been. Please shut up and go read this to begin your education: http://en.wikipedia.org/wiki/Windows_API http://en.wikipedia.org/wiki/Windows_API
- na85 12y agoDo you work for Microsoft or something? No reason to be getting so upset.
- 72deluxe 12y agoHe/she was quite blunt and rude about it, but he was right - GDI calls are Win32 API stuff or Windows API (that you don't see much of anymore, as there are wrappers for it every few years in the form of MFC / .NET etc.)
- Intermernet 12y agoI think the "hired him to shut him up" thing is a bit of a myth. From the horses mouth: http://youtu.be/o1DskPD-Ngc?t=2m21s http://youtu.be/o1DskPD-Ngc?t=2m21s . Having said that, he was quite vocal at the time, and I personally think that he may have been a large part of the huge Vista -> Win7 improvements, although have no evidence to support this. The timing just seems about right.
- nivla 12y ago>Microsoft eventually hired him to shut him up. Well i don't buy that part. When I first came across sysmon/regmon/procmon, I found it to be an amazing piece of work. An extremely small free standalone program that gave you a realtime insight into the OS? Heck, if I kept a list of people to hire, he would definitely be on it! That thing was even 1/10 of the "hello world" Go program I compiled!!!* *(~100Kb vs 1Mb) I know Garbage Collection adds a lot to size but its still a fun comparison.
- vanzard 12y agoThe large binary size of a Go program has nothing to do with "garbage collection". It's because the binaries are statically linked against the Go runtime. Try compiling a static C "hello world" program and it will be comparable in size to the Go binary.
- abcd_f 12y ago> Microsoft eventually hired him to shut him up. ... and they tasked him with this obnoxious and highly dispensable cloud computing project. Anything just to keep Mark shut up, ANYTHING.
- Slartibreakfast 12y agoMark Russinovich was hired by Microsoft for any number of reasons, not the least among them being the fact that he was easily one of the top Windows hackers out there. I can still remember marveling over the books he used to write about Windows internals - good stuff, and really made me aspire to become a better developer.
- yuhong 12y agoThe funny thing is this claim reminds me of Skywing. Yes, I am talking PatchGuard.