The Lessons of Software Monoculture

digitalsurgeon writes "SD Times has a story by Jeff Duntemann where he explains the 'Software monoculture' and why Microsoft's products are known for security problems. Like many Microsoft enthusiasts he claims that it's the popularity and market share of Microsoft's products that are responsible, and he notes that the problem is largely with C/C++ and mostly because of the buffer overflow problems."

Comments

Re:C#

[cablepokerface]

No, C# was made so Microsoft could make money off Java. By changing the name, and some keywords, they can market the next OO language to a bunch of people who never learned C++.

Haha, with such incredible lack of knowledge I am not surprised you checked the AC box. :)

Re:managed code

[Anonymous Coward]

"Umm, one who knows that it is required for proper interoperability with existing libraries?"

Yeah, I guess that's why languages like Python and Ruby which don't have pointer arithmetic can't call existing C libraries. Oh, wait... nevermind.

"One who knows more about language design than you?"

Well, at least you didn't let your emotions on the subject degrade your argument...

Re:C# was created because of business politics

[BarryNorton]

If it also solves the buffer overflow problem (I don't know C#), that is a beneficial side effect.

Which is to ignore why Microsoft were interested in a 'new' language (ok, no parametric polymorphism, no inductive datatypes, no higher-order functions etc. etc., but, oooh, array bounds checking!) like Java in the first place... You didn't really think much about your answer, did you?... (Congratulations for feeling qualified to rehash the same old rubbish about lawsuits without even knowing or thinking about the technology...)