But techies at kuro5hin, who have spent time in the company of some of the leaked Windows 2000 source code, have uncovered some interesting insights into the minds of the Microsoft authors of the software.
Two bundles of code made their way into the wild - large portions of Windows NT4 and around 15% of the total estimated 100 million lines of Windows 2000.
Kuro5hin meanders through the Windows 2000 leak. While they find the quality of the code in general to be "excellent", there are plenty of programmers' notes inserted here and there to raise a giggle amongst us, the unititiated.
The coders like a curse and kuro5hin discovers "a dozen or so 'fucks' and 'shits' and hundreds of 'craps'.
Here's an example:
// the fucking alpha cpp compiler seems to fuck up the goddam type "LPITEMIDLIST", so to work
// around the fucking peice of shit compiler we pass the last param as an void *instead of a LPITEMIDLIST
There are, it seems, plenty of morons too:
// we are such morons. Wiz97 underwent a redesign between IE4 and IE5 privateshellextftpftpdrop.cpp:
We have to do this only because Exchange is a moron.
// We are morons. We changed the IDeskTray interface between IE4
And here's another we quite enjoyed:
* CallProc32W is insane. It's a variadic function that uses * the pascal calling convention. (It probably makes more sense * when you're stoned.)
Happily, Kuro5hin concludes: "The security risks from this code appear to be low."
The code, it points out, is nearly four years old, so, "any obvious problems should be patched by now". They also find that Microsoft's fears that the code will be pirated by its competitors, "seem largely unfounded." The whole, happy tale is at kuro5hin here. µ
Firm has slashed emissions by almost 40 per cent against 2005 baseline
These 'roos are small. These 'roos are far aw... no wait, they're small as well
Firm says decision means no other firm will have to relive its 'nightmare scenario'
Firm claims cloud-based threat detection will 'stop attacks as they happen'