The defect density findings however change when Android's Linux heritage is taken out of the equation. Chou noted that the Android kernel is derived from the Linux kernel and when the parts that are Android-kernel-specific are taken out, the defect density goes up. According to Chou the defect density of Android specific kernel code was 0.7. "Android-specific code in the kernel tended to be buggier," Chou said.
Wow, you fail at reading comprehension. Miguel has never claimed that Mono *doesn't* infringe on patents because he can't be 100% certain that it doesn't, it's not the same as knowing that it *does*.
No one has been able to point us (the Mono team) at a single patent that we may infringe. Not one. You'd think, with all the rabidly anti-Mono trolls such as yourself, that one of you, after 9 years, would have come up with at least 1 solid patent infringement claim, but no.
Same old vague hand waiving claiming we infringe patents that you can't point to but just *know* exist. Sorta like some people claim to *know* that God really exists, or like many children believe with all their heart that Santa Clause really exists.
Uh, but you can. DotGNU is another implementation.
Well, you would do best by showing him how it's done. Looking forward to see your next contrib to FOSS.
LOL, yea, that'll be the day
The ego's of the anti-this/that/other-thing people is so hilarious. They love to talk big, but don't have the skills to produce anything.
It's comforting to finally read some words of wisdom!
You also touched on something I have always found so amusing. I don't know if you've noticed or not, but a vast majority of the people badmouthing Mono have not contributed *anything* to F/OSS (like the Boycott Novell trolls), who, when asked why they don't contribute, reply (more-or-less) "we don't have time, we're too busy badmouthing Mono".
Imagine if these people put their time and energy into something constructive instead, like contributing to Rhythmbox (since they obviously hate Banshee), GNote (since they hate Tomboy), or any other alternative to the Mono apps out there. If they put half the energy into that as opposed to writing hundreds of thousands of comments/articles per day bashing us and our project, they'd have nothing to worry about because the C alternatives would have far surpassed the Mono versions.
Well said, you deserve at least a +5 insightful!
I'm not sure 99% use
Why else do you suppose they scream so loudly?
There's a saying: the more powerless you are, the louder you scream about things.
Some of us have been writing C in Linux for ~12 years and decided enough is enough. C++ is not any better (in many ways worse), Python doesn't really scale and is not statically typed, and Java is in many ways inferior to C# (C# is basically Java-done-Right - altho it too has some problems, but largely it really is Java-done-Right imho).
So what other options do we have?
C#, imho, fits the bill nicely, so I worked on Mono and MonoDevelop because the better these tools are, the more productive I am (as well as many other devs) when I (we) write other free software.
If you don't like C#, fine, don't use it. Use Java or Python or whatever it is you prefer. I'm not going to badmouth your choices simply because I prefer some other language, and I expect the same in return.
We are also not "injecting patent bombs into FOSS". Microsoft has issued a legally binding statement saying they will not sue. While this promise is not perfect (ie. it won't cover partial implementations of ECMA 334 & 335), but it *does* cover Mono because Mono is a full implementation.
Besides, even if this were not the case - you've obviously chosen not to use any apps built on Mono, right? So what "patent bombs" related to Mono are you worried about?
As with all things on the Linux desktop, every app has a bajillion alternatives (some better than others). The worst thing that can happen is Microsoft attacks and everyone switches to one of the alternatives and instantly everything is resolved and Microsoft walks away with nothing (because everyone switches to something else). Woopty-doo.
Damn, wish I could mod you up because you hit the nail on the head.
Top Ten Things Overheard At The ANSI C Draft Committee Meetings: (5) All right, who's the wiseguy who stuck this trigraph stuff in here?