Comment Re:Hoax (Score 1) 689
Of course Bill is sorry. I mean, they've produced some of the most insecure and unstable code in that last couple of years and it's obviously hurt their business... wait.. that's what SHOULD be reality.
I agree with one thing - Microsoft introduced the masses to the concept of inept programming *AND* they made money from it. Good business, yes. A couple of blue-screens every now and then? Oh, that's a hardware problem.. or, perhaps, that's just "normal"..
I'd like to believe you and that Bill has been fretting over this for years. I doubt it though.
To quote a cliche, "Don't fix it if it ain't broken". I don't know - perhaps Bill tried to send out a similar email years ago and it got lost or something (I mean, it *IS* an Outlook/Exchange combination over there probably! )
Yes - Microsoft is a huge corporation with thousands of developers - with thousands of egos. But, if all it takes is Bill to send an email out to "remind" everyone to write secure and stable code, why didn't he do it years ago and save his stomach all the rolaids? Maybe it just wasn't that important to him... and to suspect any different now is just a 'bit hopeful I imagine. "Secure" Microsoft code is code that isn't broken in the press. To believe that Bill got involved in this "initiative" for any other reason than negative publicity is naive at best.
Yes - I *AM* a developer.. yes.. my management does often request features over security... but, at least I fight back. Perhaps Microsoft is so large that individuals can't do that - but given the history of their "Chief Architect", I suspect it's not a priority anyways.
I agree with one thing - Microsoft introduced the masses to the concept of inept programming *AND* they made money from it. Good business, yes. A couple of blue-screens every now and then? Oh, that's a hardware problem.. or, perhaps, that's just "normal"..
I'd like to believe you and that Bill has been fretting over this for years. I doubt it though.
To quote a cliche, "Don't fix it if it ain't broken". I don't know - perhaps Bill tried to send out a similar email years ago and it got lost or something (I mean, it *IS* an Outlook/Exchange combination over there probably! )
Yes - Microsoft is a huge corporation with thousands of developers - with thousands of egos. But, if all it takes is Bill to send an email out to "remind" everyone to write secure and stable code, why didn't he do it years ago and save his stomach all the rolaids? Maybe it just wasn't that important to him... and to suspect any different now is just a 'bit hopeful I imagine. "Secure" Microsoft code is code that isn't broken in the press. To believe that Bill got involved in this "initiative" for any other reason than negative publicity is naive at best.
Yes - I *AM* a developer.. yes.. my management does often request features over security... but, at least I fight back. Perhaps Microsoft is so large that individuals can't do that - but given the history of their "Chief Architect", I suspect it's not a priority anyways.
