The FSF speaks again on Mono, to include the Community Promise issue, and renders a verdict: The “promise is full of loopholes, and it’s nowhere near enough to make C# safe.”
One thing I really like about this article is they hit one of the mono apologists’ favorite distortions right out of the gate:
It’s true that all software patents are a threat to developers—but that doesn’t mean that all software patents are equally threatening. Different companies might have patents that could be used to attack other languages, but if we worried about every patent that could be used against us, we wouldn’t get anything done. Microsoft’s patents are much more dangerous: it’s the only major software company that has declared itself the enemy of GNU/Linux and stated its intention to attack our community with patents.
Now I’ve been preaching this gospel since Day 1. It is pure dishonesty to pretend like every company present the same risk and hostility to Linux, Free Software, or Open Source that Microsoft does. Microsoft’s hostility and desire to destroy Linux is not the fevered imaginations of wild-eyed zealots. It is documented. It is proven. It is inarguable.
Now, you may want to advance the idea that Microsoft has changed. That is a possibility, sure – but it is not documented, proven or inarguable. The safe and sane position towards Microsoft is suspicion and wariness. Microsoft made it so, not wild-eyed zealots. It also becomes on open question on what type of change it is.
You may also want to advance the idea that Microsoft’s hostility is overstated. That is a possibility, as well – but you run into a real problem with objectivity there. That is, there is no way for us to know the limits or true intention of Microsoft’s hostility. We can only know that we have more proof and evidence for Microsoft’s hostility to Linux, Free Software and Open Source than any other other entity in existence – with the arguable exception of SCO – and that we have evidence they systematically lie and disguise their intent.
What you can not honestly do, though, is to pretend like Microsoft does not have a long and documented history of unfair, illegal, and highly questionable tactics against Linux, Free Software, Open Source and even commercial competitors. You can also not pretend like it is “ancient history” or that the very same people that participated in such tactics are not still active within Microsoft.
Nonetheless, it seems if you find any discussion of Mono you will eventually run into some Mono/Microsoft apologists pretending like doubting Microsoft is irrational, if not downright cheese-eating surrender monkey cowardice. You know those hillbillies that handle snakes because they think Jesus will protect them? They aren’t brave, they are deluded. You know those guys that don’t handle snakes? They aren’t cowards, they are rational.
Offering solutions
Another nice thing that the FSF has done is to offer up an acceptable solution, as well as an invitation to Microsoft to work together to reach a real and inarguable solution.
There is an interesting point within: just as “Only Nixon could go to China”, only the FSF has the credibility to assure people that Microsoft’s offerings are valid. Novell does not have that credibility. Team Mono does not have that credibility.
When you mock the core principles of Free Software, embrace “pragmatism”, and compromise your ethics a little bit here and a little bit there, you might profit in the short term; but long term, when you go to make a stand and ask people to trust you, things are different then. In one light that is unfair, but the reality is that is what happens when you enter into anti-community and secretive deal and take $400+ million dollars from Microsoft.
Oh, and continuing to fight the FSF or rms with whatever flavor of scandal or slander you can grab doesn’t add to your credibility either. Just in case you thought it did. No, it only spreads the taint of your lack of credibility. Like a single rotten apple spoiling the barrel, so does one dishonest hateful apologist spoil a “movement”.
Sadly, this works on both sides. Which is why my arguments are always only the Purest of Logic and Reason, and I constantly refrain from personally attacking The Lying Slanderous Bastards in the Opposition.
More to come
I encourage everyone to read and think on the FSF statement. There are some interesting arguments in there, and I would like to see a much longer and detailed essay forthcoming.

#1 by Jason on July 28th, 2009
Mininova?
#2 by Jason on July 28th, 2009
TuxDistro?
#3 by Jo Shields on July 28th, 2009
Okay, I THINK this should work. I think. First time I’ve ever made a torrent. http://thepiratebay.org/torrent/5027749
#4 by Dan Serban on July 28th, 2009
64-bit? Oh …
#5 by Jo Shields on July 28th, 2009
I could be convinced to repeat the procedure for an i386 ISO, but it sounds like lots and lots of effort.
Demonstration of clicking on the map on http://childsplaycharity.org/ would be EXTREMELY motivating for me.
#6 by Jason on July 28th, 2009
@Jo,
Done. I got a Clue, Jr. game for NC, because:
1. That is where I am originally from.
2. Clue is the one of the coolest games ever.
3. The movie was pretty rocking too.
#7 by Jo Shields on July 28th, 2009
5dc36493376d0c0ada8641d959e4cd2a chickenlittle32.iso
Needs testing, SCP’ing home, and torrenting
Still not sure if the torrent works, I’m seemingly not marked as a seeder on TPB :/
#8 by Jo Shields on July 28th, 2009
Test checks out. scp’ing home.
#9 by Jo Shields on July 28th, 2009
Well, this was worthwhile, if nothing else because it means a sick kid gets a game to play.
#10 by neighborlee on July 30th, 2009
Your choice of name for this respin is certainly interesting, would you care to share your reasons for choosing it
Your comment in last paragraph about the paranoid amoung us, only serves to show your continued , laughable lack of sinerity about all of this.
But you know what Jo, it does not matter, because Fedora is leading the way to real ‘choice’, something it seems debian/ubuntu have no clue about ; and further, I suspect ‘chicks’ will feel safe there as well .
cheers
nl
#11 by zekopeko on July 30th, 2009
Jo did something that nobody amongst you complaining about mono even bothered to *try* doing. Talk about being ungrateful.
#12 by Jo Shields on July 30th, 2009
He’s helped me prove a point, meaning it was worth the hour’s investment.
#13 by Jo Shields on July 30th, 2009
I should learn to listen to people who know better, but…
Certainly. It’s a wonderful, fantastical name for three reasons:
* It abbreviates to “CLR”. The CLR, or Common Language Runtime, is one of the core parts of an ECMA335 implementation
* Given my use of one of Plunder Island’s feral chickens as my avatar, the chicken link is well-established
* The Sky Is Falling is an excellent fable, and the screams of imminent disaster are well-served by reading it, given Mono’s creation in 2001, inclusion in Debian in 2002, and inclusion in Ubuntu by default in 2006
When I say “the paranoid amongst us”, I specifically refer to people who would “look a gift horse in the mouth”. Sound like anyone you know? Obviously I’m not “sincere” with CLR, since I strongly feel that Mono is no greater risk than anything else on a desktop – but, to help prove a few points, I invested an hour (70 minutes, truth be told, including downloading the unmodified ISO and one false start). It was worth the investment, if nothing else because the price I charge for feature requests (which would include the i386 ISO) is worth charging.
I’ve taken a different route, and said “here is a gift horse. Hey, ever heard of West Nile Virus? Just sayin’…”. It is up to the end user to determine whether they think a gift horse from a “bad” person is likely to come pre-infected, and I just want to make people fully aware of exactly which electronic trust they are undertaking, from whom, and which violations of that trust are technically feasible. The paranoid will assume the worst.
So, to clarify, “real choice” means “the lack of choice _I_ want”, right? In which case, what’s wrong with CLR? Surely it’s exactly what you people have been demanding (yet not bothering to do yourselves) for months if not years?