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."
All that "popularity" can do is emphasize the problems that are already there. Ultimately, it's Microsoft's fault for letting the massive number of bugs in to begin with.
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.
"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...
Wow,,,,
I have never seen so many MS A$$-lickers in my life. What the F... this has got to do with C/C++. I thought IE was coded in VB anyway. C/C++ are just tools. You the programmer create bugs, and they just get to stay there by bad debugging and stupid assumptions as all MS products have a lot of it. I never thought that one day I see someone blaming bugs on C/C++. Maybe in the future it'll be the CPU to blame, who knows????