Why MS is Not Opening More Source Code

mario_grgic writes "Apparently inappropriate code comments is one of the reasons according to this story. I wonder what kind of things developers put in comments that would be so bad for the rest of us to see?"

Comments

more info on minigirls

[Anonymous Coward]

there is a follow up article over at MiNi Girl's Tech Report. Interesting stuff. Suposedly, they have a copy of some leaked source code and as you can see for yourself, it would be rather embarassing and a PR nightmare for Microsoft to release this code!

In related news....

[humankind]

Why do bears shit in the woods...

Why did GW Bush invade Iraq...

Why do some stories in ./ get greenlighted...

Re:See the code, be the code

[bug_hunter]

Does that mean any closed source code writer can never work again once (s)he's seen some open source code?

Re:See the code, be the code

[Spy der Mann]

And when you've glanced at it, you've doomed yourself and your Open Source company from ever using you as a developer ever again.

That's right. Who would hire a developer whose mind became infected with spaguetti code?

Re:How about this?

[Anonymous Coward]

look at this bit of 31337 c0d3 from linux:

#ifdef STRANGE_BSD_BYTE_ORDERING_THING
/* OpenBSD < 2.1, all FreeBSD and netBSD, BSDi < 3.0 */
#define FIX(n) (n)
#else /* OpenBSD 2.1, all Linux */
#define FIX(n) htons(n)
#endif /* STRANGE_BSD_BYTE_ORDERING_THING */

this is the kind type of shit you l1nux c0d3rz write. why would microsoft want that? you kiddies must have skipped school to drop acid the day that Big and Little Endian was explained in your high school architecture classes. and also that day in your college networks class (oh wait; you're not old enough to be in college) when htons was discussed in relation to network byte ordering.

for you l1nux cl00b13z, you should always call htons(3) on integers you plan to stick in a network header. htons has a platform-dependant implementation that guarantees a result in network byte order. the cl00b13 who wrote the above code not only wrote broken code, but also wrote code that, in effect, does absolutely nothing more than a simple call to htons(3).

harold gutch said it best in a comment he inserted into the "nestea" exploit, as he corrected some stupid L1nux k1dd13 c0d3: /* bsd usage works now, the original nestea.c was broken, because some braindead linsux-c0d3r was too stupid to use sendto() correctly */

Re:Some examples...

[dedazo]

• /* This code makes the stuff look like the Windows shell, because I'm incapable of innovating. Hopefully it doesn't reproduce the bugs */
• /* This doesn't really work, but I ship early and often. Maybe no one will notice. */
• /* This doesn't work either, but windoze is teh suxx0rz */
• /* I'm sure this infringes on some copyright, but it doesn't matter. It's OK because I want it to be */
• /* I can't get laid but my random number generator is teh roxx0rz */
• /* This is where we initiate a gratuitous TCP connection */
• /* This looks ugly but noone will notice anyway, fonts in Linux look like shit */
• /* Let's link to this nifty library and then forget about it when someone finds a hole in it */
• /* This seems to segfault in my machine, hopefully not yours. Hopefully */
• /* I'm so cool */