If I give credit when it is due, then I must lay blame as well. That is the nature of being a rock of unbiased objectivity in the poop-storm of propaganda. Such is the thankless task to which I now apply myself.

I have never understood why mono apologists take so many talking points from Jo Shields. The gentleman may be a great packager and contributor, I don’t know,  but his arguments are terrible and credibility is poor. Let’s take a look at why I say that:

Consider that we know for a fact that F-Spot and Banshee, at least, use non-ECMA covered parts of mono. Maybe they will be re-written soon. That’s great. But at the time of the announcement and currently, they were and are not covered by the standard, and so not covered by the agreement.

Right, then. So we have Mr. Shields gleeful announcement on the Ubuntu Forums:

Re: Monolith

Quote:
>Originally Posted by zekopeko
>hahahahaha!!!! well it looks like sane people will stop bitching about ECMA standards at least.
>does this cover the ASP.NET , ADO.NET, System.Windows.Forms?

No. But nobody cares about those – they aren’t used for the apps people moan about

This is blatantly false, but I guarantee you the mono-men on the Ubuntu Forum that parrot Mr. Shields will not soon tire of repeating it.

We have his careless “glossing over” the distinction on his own blog’s announcement:

If the anti-Mono crowd were provided with their GPL-compatible patent grant for Mono, which they spend so much time talking about the absence of, how would they react?

Of course, there is no such GPL-compatible patent grant for Mono, and such promises have already been called into question last year by the Software Freedom Law Center. I will freely admit that I consider the Community Promise a positive development in the context of making Mono safer – but over-selling it doesn’t bolster your position, it hurts it.

We have him attacking Stallman’s incorrect assessment of Tomboy using non-ECMA parts, conveniently not mentioning many important mono apps which do indeed use non-ECMA parts. If Stallman gets a point like that wrong in a project he is not personally involved in, that is an honest error. If you get a point like that wrong in a project you are personally involved in, well, let’s just say it doesn’t look like an honest error.

We have this strange assertion on his own blog :

So is Mono “always playing catch-up”? Not on anything anyone who isn’t porting from Windows cares about. And Mono wasn’t created with that goal in mind. For making apps which look and feel at home on Linux, we’ve had what we need for years.

Yet, the Mono General FAQ suggests otherwise:

Why is Novell working on .NET?

There are two reasons:

  • Increase developer productivity.
  • Assist Windows .NET developers to deploy their applications on Linux.

These are admittedly small things in the overall picture, but I do think they speak to a general dearth of reliable pro-mono arguments from Mr. Shields.

Part of the problem is the the large portion of the debate is over opinions – it takes disproportionately strong arguments to change someone’s opinion. You aren’t going to get very far calling people’s opinions “idiotic”, “paranoid”, “religious”, etc. etc. If you want to continue to attack people’s opinions, well good luck with that.

Mono apologists never learn this, especially when they portray people’s distrust of Microsoft as paranoid or irrational. Any sane man on the face of the earth will freely admit some distrust of Microsoft is perfectly rational, justified, and even required. Reasonable people can disagree on exactly how much distrust is warranted.

That leaves a smaller portion to factual debate. And so, when mono apologists get the facts wrong, or gloss over inconvenient facts, even when they are small facts – it greatly damages credibility.