Linked by Thom Holwerda on Mon 14th Dec 2009 23:52 UTC
Windows Ah, MinWin. The elusive project in the Windows team that has been misunderstood more times than I can count. Once again, Mark Russinovich, more or less the Linus of the Windows world (I win stupidest comparison of the year award), has explained what MinWin is all about, while also touching upon a number of other changes to the core of Windows. Before we start: thanks to BetaNews for once again detailing these technical talks regarding the core of Windows so well.
Permalink for comment 399714
To read all comments associated with this story, please click here.
Member since:

Well, I understand what you're saying, and perhaps you're right, but I take issue with it being called a back-handed compliment. I really was being sincere: I do think the alternatives are marginally better -- or at least, I've found them to be so for my daily work. I left Windows because I was sick of it, and the alternatives just worked better. I was making a value judgment, but it was based on pragmatic considerations.

I regretted the 'intentionally write bad code' bit -- that's not what I meant to say. I think the Windows developers write a huge pile of good code, and their backwards-compatibility efforts are especially noble and sacrificial. But someone, somewhere, either was sloppy or was forced to write bad code (for whatever reason, bureaucratic, architecture, or otherwise). Otherwise, their engineers wouldn't be attempting to fix it.

We all write bad code -- I've written a pile of it. As developers, true honesty recognises that we're all in a state of learning, and we'll never reach some sort of absolute pinnacle. This is all I was saying -- that it's easy to think we're perfect and they just don't give a damn, and I found it refreshing to be reminded that this just isn't the case.

Reply Parent Score: 1