Even the apps that Microsoft themselves have written (e.g. SCOM) are pretty poor. That's fine for enterprise software, servers and so on where you can easily throw more hardware at the problem, but I'm very thankful that of the 100-ish processes running on my laptop at the moment, most are not written in C#. Also, Microsoft have recently been stating their intention to bring back some focus to native (C++) development for Windows.
Though, I feel C++ is sub-optimal as a native language, given how easy it is to shoot yourself in the foot. It doesn't have to be so dangerous to write performant native code. Why is it that D never really took off?
We also might want to take a statement on the security of a platform by a company that makes their money securing people's computers with a grain of salt or two
Further, its astounding the amount of fear mongering I've seen from security firms and windows "security experts" over the past several decades. Literally they make their money by scaring people into buying tools.
I believe you need those tools if you run Windows, but you don't need them if you run Linux or OS X.
Btw., interestingly, Apple starts to use ObjC more and more on MacOSX. E.g., since 10.6, Finder (the main fs browser) is a Cocoa application now. I guess the Windows Explorer is still C++?
The idea that C# is superior (and by the way, the OS is not written in C#) to Objective-C for security is asinine.
The way Objective-C has been handling memory management since its inception is far better than most of the other languages around.
And the decision to have deliberate mutable/immutable data structures is something ALL languages should have.
How about this, lets look at application programming language. Apple uses objC, Microsfot increasingly uses C#. What does this one metric get us?
I believe it was Paul Graham himself who 10 years ago mentioned that to scale a company you should have your top developers just develop the tools the rest use. This was also around the time Microsoft was at the height of the buffer over flow bugs.
Slowly they transitioned much of their code to the memory managed language of C# that their best developers made.
Their entire development process, developer allocation and development language changed in part in order to meet security needs.
Mean while Apple still develops everything in un memmory managed objC.
That's just one example of how long Microsoft has been transitioning the entire company to new more security focused practices.
The point is, to be really good at security, you have to be really focused on it, at all levels, in an all encompassing way. Microsoft has been transitioning to that for a long time and it's paid off. Apple hasn't even started. And that kind of massive corporate change in companies this big doesn't happen over night. And look how much public shaming it took to kick it off for Microsoft. I think we can look forward to a new golden age of Mac insecurity over the next few years before the process even kicks off.
And this is probably how Kaspersky Lab came to say that Apple is 10 years behind Microsoft on security.