It’s always important to consider things that would change your mind.
Here is a quote that I like:
“You cannot reason a man out of a position he has not reasoned himself into.”
- Ben Franklin
If you are in an argument with someone, and you ask them “Well, what would it take for you to change your mind, then?” And they answer “Nothing!”, then walk away. No amount of rational discourse will reach that person.
I like to think I have reasoned myself into my current position; I certainly didn’t get up one day and throw a dart at a board and decide to hate on Mono for a while. So, one of the things I have to do is to challenge myself by asking “What would it take for me to change my mind?”
Not one thing is either necessary or sufficient, but more list of solutions to problems I see.
On Trusting Microsoft
This is the big one, because a lot of the concern is that Microsoft has it in for Linux and will do something, sometime to hurt it. What we need is some assurance that prevents Microsoft from unfairly crippling Linux. That is, if somehow Microsoft released a Windows so glorious that the whole earth’s population desired it, that’s one thing. But if Microsoft gets down to about 40% market share, falling fast, and calls in Darl McBride, that’s another thing.
Microsoft joins the OIN.
Yeah, that would be undeniable proof it is a new day. We see all up and down in Microsoft internal emails that Microsoft considers how to use patents against competitors. That doesn’t necessarily mean dragging them into court – threating and waving them around and then coming in for some sort of “agreement” is aggressive use of patents, too. Joining a patent defense organization like OIN would be a major signal Microsoft is ready to compete on merit and not legal trickery.
Microsoft talks honestly about Linux and Open Source
People specifically hired to spin Open Source do not count. I mean Executives, the kind with a golden toilet on the Lear Jet. People that matter and have a real say in Microsoft strategy. I don’t doubt that Joe McCoder, the new hire, thinks Open Source is nifty. I do doubt Joe McCoder, the new hire, has bumbley-squat to do with Microsoft policy.
Microsoft replaces Ballmer with someone non-psychopathic
On a related note: with Ballmer in charge, it’s just hard to really believe that Microsoft is doing anything more than being cold and calculated (poophouse crazy is an alternative). Get respectible people in charge.
Microsoft releases some interesting code, GPL style for bonus points
We almost got there with this virtualization code. There’s nothing really wrong with Microsoft releasing code they benefit from, it is to be expected. Except now it turns out it might be something they had to do because of a possible GPL violation. Which poops all over the whole thing.
Still, if they released some code that was useful all around, and it was GPL, each bit would move me that much closer to treating Microsoft less hostile. This is because the more Microsoft has invested in the Open Source community, the less likely it is they will turn around and attack us. Some people think Microsoft is already at, or closely approaching that point. I don’t think so.
Microsoft releases a linux distro
Why not? They had XENIX right? And they might even be able to make a business case out of it: “If you have to use Linux, use Microsoft Linux!”. This is because I believe the GPL protects us well enough that even such an … unexpected … move by Microsoft would only reap benefits in the community. Plus, with Microsoft Linux, Ubuntu users would finally have a distro to look down on! It’s a win-win!
Time passes peacefully
One of the problems Microsoft faces is that they have such a long and rich history of hostile behavior. How does one realistically trust an entity like that? Say they were “evil” for 10 years, then say “Oh, we changed!”. Do you trust them on year 11? Year 15? Year 20? What if they keep doing things that are offensive? Year 25?
Microsoft keeps doing things that are offensive. It’s a sort of 1-step-forward, 2-steps-back thing. More steps forward, less steps back, please.
Also it would help if people would stop pretending that distrusting Microsoft is some sort of irrational response. Here is another saying I like:
Extraordinary claims require extraordinary proof.
-Marcello Truzzi
Claiming that Microsoft is “Open Source Friendly” is an extraordinary claim. Just saying it is not enough. It will take time, actions, and words to get people to accept that. Don’t pretend like people are nutbars because they feel the burden of proof hasn’t been met yet – especially since those people probably aren’t all that interested in what Microsoft is offering anyway.
Let me just expand on that a bit: a lot of the “give Microsoft a break already” people have a financial or other ulterior motives. Hearing it from them doesn’t help a whole lot – it can even backfire. Hearing it from people who are unrelated to anything Microsoft helps a lot more.
On Trusting Mono / Moonlight / Novell
A Credible Endorsement
This really applies all around, but I’ll stick it here.
One of the reasons I don’t go on about the Open Specification Promise is that Red Hat indicates they are alright with it. I figure Red Hat knows what they are doing, so drive on. That’s the advantage of retaining your integrity, when you say something people believe you.
This is also why I think Stallman has been attacked so fiercely. If he were to speak approvingly of C#/Mono, I think most people would accept that and move on. I would certainly relax – in fact, I had relaxed and “given up the fight” until he came out and explicitly called for it to be discouraged.
Novell comes “back into the fold”
Novell does not renew its deal with Microsoft, and competes as Red Hat does. Drop all that “piece of mind” and any similar talk. Do not accept or promote exclusive Microsoft-Novell arrangements. Yes, yes, I know they aren’t the only company to strike deals with Microsoft. But they are who we are talking about here.
Mono focuses on OpenSuse or a new distro
One of the things that bothers me is how much focus there is on getting Mono into Debian/Ubuntu/GNOME. I think I understand why, but it seems that Mono is trying to “ride the coat tails” of the most popular distros/DEs, and leverage Miguel’s relationship with GNOME.
We see a number of Windows titles come to Linux via Mono
On a practical note, I like cool software just as much as anyone. If I saw a lot of cool Windows software coming over via Mono, I’d be inclined to look a little more favorably on Mono. As it is now, Wine is much better in this particular area, and doesn’t have the nasty promoting Microsoft vibe that I dislike about Mono.
Which is strange, because Mono apologists seem to love to point out how Mono/Wine are similar, while ignoring that Wine isn’t in the default install, nor are people seriously suggesting using Wine as an important development platform.
If Mono was a good as they say it is
This is a tough one, but if Mono was as good as it is talked up by the promoters, then it might be worth the risk. That is, if it helps developers become crazy productive, then it might be something worth the fight if it should come to that. A much much weaker version of this would apply to the individual apps themselves.
Not to put down the hard work done by mono developers, but lynchpinning Mono inclusion on a note-taking app and then arguing about comparative features makes the whole shebang look weak. It’s a freaking notetaking app, not a cure for cancer.
If I didn’t think the promotion/defense was dishonest
There is still a little bit of this – the original reason why I became anti-mono – but I think most of it has been hashed out. It doesn’t mean I agree with all I’ve heard, but I used to think there wasn’t any honesty at all! I don’t mind disagreeing if I think both people just have a different view on things; I just don’t like feeling like I am being lied to.
One thing that helped me in this area is after the Community Promise event I changed my strategy for this blog. I promised that I would not go back in time and pick apart past arguments, instead I tried to post my reasoning and answer direct questions. I found that made me try a lot harder to articulate my position and also struggle to answer some mono defenses. If I had just focused on finding old fallacious arguments, I think things would have went in a very different direction! (They would have been much easier on me, for one thing, I can tell you that.)
Work on presentation
I sympathize that one grows tired of defending something. The best response I can have to that is people had to know what they were getting into by “embracing” Microsoft. To be honest, I really think the Mono PR badly badly stumbled from day one, and has never really gotten much better.
Consider this: Mono apologists like to compare Mono and Wine. Lots of people “hate” Mono. Not lots of people “hate” Wine. Look at it just from a PR standpoint. How is Wine presented compared to how Mono is presented? Perhaps technical-minded people don’t think presentation matters, that a technical argument towers over everything. That belief is wrong. Think of all the technically superior products and technologies that “lost”. Technical arguments go a long way, but they don’t go the distance.
What about you?
Can you even consider what it would take to move you to the other side? Can you even acknowledge the other side might have a point?
For example, I would ask the pro-mono contingent, exactly how aggressive would Microsoft have to get with patents before you think it is a real concern? Obviously more than internal emails, normal Microsoft FUD, Tom-Tom and Buffalo. Is there any patent action that Microsoft could take that would alarm you in this area?
Or, how about anti-community, exclusive agreements? Mono is not too bad in this area. Moonlight is much worse. What if Novell struck a new deal with Microsoft that was even more “Novell-only”? Would you protest, or just shrug and accept it?
Or, how about what level of disagreement do you think is appropriate for something you just don’t approve of? Is any level of public criticism acceptable? Is it ever acceptable for people just to say “I don’t want that”? Is it ever acceptable for people just to say “I don’t want that, and I don’t want it in my distro, and I’m going to let people know”?
We throw around “zealot” and “shill” like it is nothing, but some people on both sides genuinely hold the point of view they espouse. Yeah, yeah, the internet is serious business, I know – but if you are intellectually honest, you need to examine all sides of the argument as best you are able. If, on the other hand, you are in it for the lulz, fast cars and supermodels, well then …. you have chosen poorly.

#1 by Jo Shields on July 24th, 2009
There are a whole bunch of points here that I wholeheartedly agree with. No, really. I’ll go down your list one section at a time, to tell you my own feelings on those topics. You might be surprised.
What a FASCINATING idea. I can even see the positives for them – they get attacked all the time with patent suits, and it’d strengthen their defenses to have, say, the Commerce One patents to beat attackers with. The current OIN structure would need to be refreshed though (as it’s entirely Linux-centric) and any such agreement would absolutely need to be “fair” (i.e. RH et al patents in the OIN being used to defend MS from attacks). Unfortunately, I doubt the shareholders would allow it.
Microsoft, as a huge company, is split into lots of divisions and subdivisions. I think some divisions are already MUCH closer to honest talk than others. Developer Tools (the people behind .NET) are actually fans, which is why they’ve been releasing a bunch of things under a Free license lately, and taking back too (JQuery in Visual Studio). Other divisions, say Entertainment and Devices (who own the DRM group). Really, I think it’s customer driven – the Tools customers are demanding more openness (and getting it), the DRM customers are, well…
The man needs to leave the company today, for the good of the human race. And I’m not exaggerating my feelings there.
Depends on your definition of interesting, really. They’ve already released a bunch of .NET stuff under their Ms-PL license (which is DFSG, OSI and FSF-Free, before anyone asks), which Mono is able to take advantage of. Again, it’s all coming from the Tools group, really. I don’t see the Xbox team releasing any source any time soon.
Other than for the lulz, I’m not sure why they’d want to do so. It’d cost them too much for them to make it a credible alternative to RH et al.
I doubt this is gonna happen until Ballmer’s been shot into the sun. The infuriating part of it is, though, that as a huge company (as previously mentioned), good actions from one group are cocked up by another group. To an extent, the company is too big for its own good – and ours.
This is gonna be controversial, but I don’t think Stallman is credible on this point – and I have some precedent to back myself up. Firstly, I’m concerned – very concerned – that in the FSF statement here, they make a bold claim which can easily be proven wrong – that Tomboy uses non-standard Microsoft libraries.
Really, try it at home, kids:
directhex@desire:~$ for i in /usr/lib/tomboy/Tomboy.exe /usr/lib/tomboy/addins/*.dll; do echo non-ecma libs in $i:; monodis –assemblyref $i | grep System | grep -v System$ | grep -v System.Xml$; done
non-ecma libs in /usr/lib/tomboy/Tomboy.exe:
non-ecma libs in /usr/lib/tomboy/addins/Backlinks.dll:
non-ecma libs in /usr/lib/tomboy/addins/Bugzilla.dll:
non-ecma libs in /usr/lib/tomboy/addins/Evolution.dll:
non-ecma libs in /usr/lib/tomboy/addins/ExportToHtml.dll:
non-ecma libs in /usr/lib/tomboy/addins/FileSystemSyncService.dll:
non-ecma libs in /usr/lib/tomboy/addins/FixedWidth.dll:
non-ecma libs in /usr/lib/tomboy/addins/InsertTimestamp.dll:
non-ecma libs in /usr/lib/tomboy/addins/NoteOfTheDay.dll:
non-ecma libs in /usr/lib/tomboy/addins/PrintNotes.dll:
non-ecma libs in /usr/lib/tomboy/addins/SshSyncServiceAddin.dll:
non-ecma libs in /usr/lib/tomboy/addins/StickyNoteImport.dll:
non-ecma libs in /usr/lib/tomboy/addins/Tasque.Addin.dll:
non-ecma libs in /usr/lib/tomboy/addins/WebDavSyncService.dll:
If it can be shown that easily that they haven’t done their research, then it gives pause for thought. Then, throw in this flame war from the 90’s where Stallman tells people not to use (Free) Tcl, for entirely bogus reasons, simply because he wants his own preferred language to be used instead: http://www.vanderburg.org/OldPages/Tcl/war/0000.html
It gives me pause. Perhaps the Tomboy claim is a simple mistake, and he’s grown up since ‘94, and he’s dead right now – but I think the assumption that he’s always right needs to be rethought.
Would endorsements help? Probably.
I think any Novell-centric patent deals are ungood, and would gladly welcome a return from that – but I think that out of all the companies “in the community”, Novell are the ones with the biggest mindshare at Microsoft – and I reckon any cooperation should be maintained (as long as it’s not at the expense of the wider community, as the patent deal was)
The direction of push & shove doesn’t go the way you think it does – other than in SUSEland (where I feel poor app decisions have been made to showcase Mono). Packagers package things that take their fancy. Desktop people pick apps which take their fancy. The only case I’m personally aware of (though I’d gratefully be corrected here) of a Novell person “pushing” their package on any other distro is a Novell employee who approached the Debian Mono Group and offered to do the packaging work for the libraries he’s been working on (a set of libs which allow WinForms apps to use the Gtk+ accessibility toolkit Atk for disabled access). Much like Microsoft offering kernel drivers, the work needed to be checked over and fixed, but we’re not going to reject the work on the basis of where it came from.
I try to avoid emaphasizing any similarities to Wine, since it’s not why Mono was initially created (it’s simply where customer demand has enhanced it in recent years). To an extent, I think the problem here a lot of the time is an image problem (which I’ll touch upon in one of your later bullet points).
It’s good. It really is. As a distro, we have about 40 apps packaged which use it, of which 4 are the “showcase” apps (Tomboy, F-Spot, GNOME Do, Banshee). This one is going further down into the image bullet too.
Years of constant drudgery can wear a person down, and at times, resort to short-cuts, cheap shots, and at times outright “truth enhancement”. And, I hate to say it, but it’s fairly annoying that whenever you make a contribution to Free Software, to have some demagogue come along and attack you personally for it. I seem remarkably good at it. Amongst Windows-centric communities, I’m seen as the Linux extremist. Amongst (certain) Linux-centric communities, I’m Ballmer’s bastard stepson.
When the mild-mannered, fully considered explanations get you nowhere, you give up on decorum. I once sat down & gave Roy a couple of thousand words on my motivations etc – and he (of course) outright ignored them. Why bother, when the moral high ground doesn’t go anywhere?
Ah, this is a tricky one. And, I hate to say it, but the critics have largely helped cause (or at least accentuate) the issues. Developers will consider having a merry ol’ time with Mono, then pick something they consider less good, purely because they don’t want to deal with the bullshit attacks that would inevitably follow if they went with the top choice. That meaning users avoiding it, other developers sneering at it, and so on. I won’t name names, but I spoke to a developer at UDS who had followed this road – and I think it’s absolutely horrible that things like this come up.
Mud sticks. And Miguel’s over-enthusiasm (I think I’ve mentioned this) in his 2002 Register interview has, to this day, haunted the project – aided by, say, people putting quotes from it in rotation in their site footer to help drive the point that BAD THINGS ARE COMING YOUR WAY.
This is largely why the project as a whole went silent on the PR front for a few years – engaging with people didn’t help in the 2002-2005ish days (Miguel’s clarification of the Reg interview was simply not enough for many, and the “Miguel is evil” vibe carried on from that day), and they pretty much stopped responding from 2005ish, in a “ignore them and they’ll go away” effort. I suppose it’s largely my fault for re-igniting a lot of the old arguments, starting in 2008, when I decided I wasn’t going to ignore the shrill and uneducated voices (e.g. Roy) whilst moderate people started to believe those points. Hell, I was absolutely appalled when I found even _I_’d been taken in by sufficient regurgitation of certain talking points leading back to Roy (I had ended up defending things that weren’t even the case).
So, there’s an image problem. Short of hiring a hit squad, any ideas how to deal with it? Because I can promise you, even if Microsoft swooped in, offered the full MS.NET source code under GPLv3, muffins for life for all Mono developers, and cake for all, it wouldn’t be enough to heal the irreconcilable problem people fundamentally have with the idea of Free Software developers encouraging something which can be traced back to Microsoft.
There’s no way to “win” this one. I really don’t think there is.
Your last point I’m going to take on in full, rather than just the heading.
I’ve been pretty pain with my feelings. All I want before knifing the baby is some tangible reason to do so. That’s it.
Any distro receives a C&D regarding core Mono components, I work to pull it from Debian/Ubuntu. A C&D against non-ECMA libs (e.g. WinForms), I’d take a decision closer the time – but I imagine I’d be in favour of amputating the dangerous sections outright, and discussing complete removal with more senior people than myself.
Clear enough?
I don’t want to reveal the content of any private conversations, but I strongly believe Occam’s Razor applies to the Moonlight wording – the people at Microsoft behind it simply failed to grasp why it was a problem. I have faith that a better, less Novell-centric wording is in everyone’s interests (including Microsoft’s), and that the parties responsible know it. The agreement needs to be refreshed anyway for SL3, so let’s see how it goes.
http://www.youtube.com/watch?v=dib2-HBsF08 ?
Here’s a level I disapprove of: someone downloading my CV from my website in order to insult me for it, line by line, on Linux Today. The Fink/Lefty incident. And so on.
My problem is people saying “I don’t want that” who simply haven’t researched the issue – they’re just recycling talking points. They’ve heard scary words and, like, zomg!
I wish people who are relying upon the good graces of thousands upon thousands of contributors to present them with a polished, quality, free and Free operating system could give those people a LITTLE more credit.
Is “let’s see YOU do better” really such a heinous response to people who criticize you for contributing?
I’m sure you won’t believe this, but I had actually intended on blogging about a similar topic soon – about the unbridgeable gulf between the “sides” of the “debate”.
The problem from my “side” is that cogent, well-thought out points are drowned in feces. Let’s take an example – I personally found this particular post quite interesting, and don’t particularly resent the hour or two I’ve spent prepping this reply. However, when you’re dealing with two polar “camps”, that means you’re lumped in with the person (BN commenter) comparing Mono to terminal disease, person (BN commenter) using Nazi symbolism to push an anti-Microsoft agenda, person (BN fanatic) trying to get someone fired for not joining them in hating Mono, and so on. Is it, perhaps, easier to group everyone together with the lowest common denominator’s labels, since it removes the need to bother replying? Yeah. But then we’re back to the “give up on decorum” from above.
#2 by Lex on July 24th, 2009
Personally I would never consider mono for development. However I would have no problem with mono applications all over a Linux distribution (by default or not) if and only if
there was a nonrestrictive (without 100% compatibility or any other restrictions) legally binding document from Microsoft opening (license and patents) the .NET platform including every standard library in a way so that a complete .NET implementation with all the standard libraries can be legally (including patents) created and distributed by anyone. (By standard libraries I mean any libraries distributed with a Microsoft .NET installer and are visible to the .NET runtime).
If they want to be open. This is open, fair in square. In my opinion anything short of that has the effect of Mono giving Microsoft a leverage against GNU/Linux. Whether they use that leverage or not is another question. My point is that they should not be given any to begin with.
#3 by woods on July 24th, 2009
@Jo
According to this
http://rofrol.wordpress.com/2009/07/23/what-non-ecma-libraries-tomboy-is-using/
Tomboy _does_ use non-ecma libraries.
So either none of those references in the source is used (and dropped at compile-time which of course means Tomboy doesn’t use them at run-time and all is fine) or there’s something wrong with your script.
#4 by Richard on July 24th, 2009
Amusing. See, “using” statements import namespaces, not assemblies. And an external assembly is only linked if it is referenced by the compiled assembly, which means that a bunch of using-statements can refer to System.Linq, but unless you’re actually using LINQ it makes zero difference to the output.
In short, the guy’s comparing namespaces to assemblies, and that’s funny
.
#5 by Jason on July 24th, 2009
@Jo,
Thank you very much for taking the time to prepare such a considered reply.
I think we are of like mind on many of those points. Let me question you a little bit more on one thing, I’m not sure I explained myself or perhaps I misunderstand you:
Although I appreciate this answer, I was asking in a more general sense. Can Microsoft reach an agressive point with patents – not necessarily specifically against Mono – where you decide the risk is to great, at least on non-ECMA components?
Say, for example Microsoft brought massive multiple patent cases against major parts of the FLOSS ecosystem: Wine, X, ALSA, whatever. Is there some point there where you would say, “Oh my” and put Mono down?
On Moonlight
I fully expect the next agreement to be more acceptable, as well. I myself used to point out that it only covered Moonlight 1, and noticed that it updated shortly after Miguel addressed one of my comments somewhere. Coincidence I’m sure, but it did get me to start thinking that maybe someone out there was listening to critics.
On the disapproval levels
Yes, going after your CV or someone’s livelihood is some villanous, cowardly junk. No argument whatsoever here on that.
On presentation
Actually, yes. It is something I have given some thought to, but I don’t have it all developed in my mind yet. Plus I can’t give you ammo to use against me!
Yeah, and not talking junk, but the clarification (“longreply”) isn’t as effective as it needs to be. I’ve read it several times and I think it misses the mark, especially as a direct rebuttal to the Register article.
On drowing points in feces
I sincerly hope you do blog on a similar topic – I will be interested to hear some assertions on your end. Not that I don’t greatly appreciate your answers – I do – but I would like to hear you start a conversation on it as well.
You’ll get no argument from me that some people simply won’t listen to reason or even facts – though I don’t think it is a problem exclusive to mono critics.
You should also realize there are a lot of people who want to be convinced Mono is A-OK, but that is one hell of a hard sell. It doesn’t mean people won’t change, but it does mean it will probably take a lot more than you think reasonable to get them to change.
#6 by Jason on July 24th, 2009
@Richard,
I think I understand, but don’t you think that might be a tricky point to get across to some people?
#7 by Richard on July 24th, 2009
It might be, but it’s the difference between being misinformed and informed. If they want to know the short answer to “Does Tomboy use non-ECMA libraries?”, that answer is “No”. If they want to know the long answer, then they need to make some attempt to understand how assemblies and namespaces work
.
The real problem comes in when you have people who want to know the long answer, as long as it’s what they think it is.
#8 by Jo Shields on July 24th, 2009
It might, if one assumes untrustworthiness. Frankly, I thought people understood how namespaces relate to libraries back in the days of Java.
For completeness, your records, etc, here’s the same analysis on the other three main Mono showcase apps. I’ve explained what they mean in a previous blog comment, I believe.
jms@osc-franzibald:~$ for i in /usr/lib/f-spot/*.exe /usr/lib/f-spot/*.dll /usr/lib/f-spot/extensions/*.dll; do echo non-ecma libs in $i:; monodis –assemblyref $i | grep System | grep -v System$ | grep -v System.Xml$; done
non-ecma libs in /usr/lib/f-spot/f-spot.exe:
Name=System.Web
non-ecma libs in /usr/lib/f-spot/Cms.dll:
non-ecma libs in /usr/lib/f-spot/FSpot.Core.dll:
non-ecma libs in /usr/lib/f-spot/FSpot.JobScheduler.dll:
non-ecma libs in /usr/lib/f-spot/FSpot.Query.dll:
non-ecma libs in /usr/lib/f-spot/FSpot.Utils.dll:
non-ecma libs in /usr/lib/f-spot/FSpot.Widgets.dll:
non-ecma libs in /usr/lib/f-spot/gio-sharp.dll:
non-ecma libs in /usr/lib/f-spot/libgphoto2-sharp.dll:
non-ecma libs in /usr/lib/f-spot/Mono.Google.dll:
Name=System.Web
non-ecma libs in /usr/lib/f-spot/Mono.Tabblo.dll:
non-ecma libs in /usr/lib/f-spot/NDesk.Glitz.dll:
non-ecma libs in /usr/lib/f-spot/SemWeb.dll:
Name=System.Data
Name=System.Web
non-ecma libs in /usr/lib/f-spot/SmugMugNet.dll:
non-ecma libs in /usr/lib/f-spot/Tao.OpenGl.dll:
non-ecma libs in /usr/lib/f-spot/Tao.OpenGl.ExtensionLoader.dll:
non-ecma libs in /usr/lib/f-spot/Tao.OpenGl.Glu.dll:
non-ecma libs in /usr/lib/f-spot/extensions/BeagleService.dll:
non-ecma libs in /usr/lib/f-spot/extensions/CDExport.dll:
non-ecma libs in /usr/lib/f-spot/extensions/ChangePhotoPath.dll:
non-ecma libs in /usr/lib/f-spot/extensions/DBusService.dll:
non-ecma libs in /usr/lib/f-spot/extensions/DevelopInUFRaw.dll:
non-ecma libs in /usr/lib/f-spot/extensions/FacebookExport.dll:
non-ecma libs in /usr/lib/f-spot/extensions/FlickrExport.dll:
non-ecma libs in /usr/lib/f-spot/extensions/FolderExport.dll:
Name=System.Web
non-ecma libs in /usr/lib/f-spot/extensions/GalleryExport.dll:
non-ecma libs in /usr/lib/f-spot/extensions/HashJob.dll:
non-ecma libs in /usr/lib/f-spot/extensions/MergeDb.dll:
non-ecma libs in /usr/lib/f-spot/extensions/PicasaWebExport.dll:
Name=System.Web
non-ecma libs in /usr/lib/f-spot/extensions/RawPlusJpeg.dll:
non-ecma libs in /usr/lib/f-spot/extensions/SmugMugExport.dll:
non-ecma libs in /usr/lib/f-spot/extensions/TabbloExport.dll:
non-ecma libs in /usr/lib/f-spot/extensions/ZipExport.dll:
jms@osc-franzibald:~$ for i in /usr/lib/banshee-1/*.dll /usr/lib/banshee-1/*.exe /usr/lib/banshee-1/Backends/*.dll /usr/lib/banshee-1/Extensions/*.dll; do echo non-ecma libs in $i:; monodis –assemblyref $i | grep System | grep -v System$ | grep -v System.Xml$; done
non-ecma libs in /usr/lib/banshee-1/Banshee.CollectionIndexer.dll:
non-ecma libs in /usr/lib/banshee-1/Banshee.Core.dll:
non-ecma libs in /usr/lib/banshee-1/Banshee.Services.dll:
Name=System.Data
Name=System.Web
non-ecma libs in /usr/lib/banshee-1/Banshee.ThickClient.dll:
non-ecma libs in /usr/lib/banshee-1/Banshee.Widgets.dll:
non-ecma libs in /usr/lib/banshee-1/Hyena.dll:
Name=System.Data
non-ecma libs in /usr/lib/banshee-1/Hyena.Gui.dll:
non-ecma libs in /usr/lib/banshee-1/Lastfm.dll:
Name=System.Web
non-ecma libs in /usr/lib/banshee-1/Lastfm.Gui.dll:
non-ecma libs in /usr/lib/banshee-1/Migo.dll:
Name=System.Web
Name=System.Data
non-ecma libs in /usr/lib/banshee-1/Mono.Media.dll:
non-ecma libs in /usr/lib/banshee-1/Mtp.dll:
non-ecma libs in /usr/lib/banshee-1/MusicBrainz.dll:
non-ecma libs in /usr/lib/banshee-1/Banshee.exe:
non-ecma libs in /usr/lib/banshee-1/Beroe.exe:
non-ecma libs in /usr/lib/banshee-1/gconf-schema-extractor.exe:
non-ecma libs in /usr/lib/banshee-1/Halie.exe:
non-ecma libs in /usr/lib/banshee-1/Muinshee.exe:
non-ecma libs in /usr/lib/banshee-1/Nereid.exe:
non-ecma libs in /usr/lib/banshee-1/Backends/Banshee.Gnome.dll:
non-ecma libs in /usr/lib/banshee-1/Backends/Banshee.GStreamer.dll:
non-ecma libs in /usr/lib/banshee-1/Backends/Banshee.Hal.dll:
non-ecma libs in /usr/lib/banshee-1/Backends/Banshee.NowPlaying.X11.dll:
non-ecma libs in /usr/lib/banshee-1/Backends/Banshee.Unix.dll:
non-ecma libs in /usr/lib/banshee-1/Extensions/Banshee.AudioCd.dll:
non-ecma libs in /usr/lib/banshee-1/Extensions/Banshee.Bookmarks.dll:
Name=System.Data
non-ecma libs in /usr/lib/banshee-1/Extensions/Banshee.BooScript.dll:
non-ecma libs in /usr/lib/banshee-1/Extensions/Banshee.CoverArt.dll:
Name=System.Data
non-ecma libs in /usr/lib/banshee-1/Extensions/Banshee.Daap.dll:
non-ecma libs in /usr/lib/banshee-1/Extensions/Banshee.Dap.dll:
non-ecma libs in /usr/lib/banshee-1/Extensions/Banshee.Dap.Ipod.dll:
non-ecma libs in /usr/lib/banshee-1/Extensions/Banshee.Dap.MassStorage.dll:
non-ecma libs in /usr/lib/banshee-1/Extensions/Banshee.Dap.Mtp.dll:
non-ecma libs in /usr/lib/banshee-1/Extensions/Banshee.FileSystemQueue.dll:
non-ecma libs in /usr/lib/banshee-1/Extensions/Banshee.InternetRadio.dll:
non-ecma libs in /usr/lib/banshee-1/Extensions/Banshee.Lastfm.dll:
Name=System.Web
Name=System.Data
non-ecma libs in /usr/lib/banshee-1/Extensions/Banshee.MiniMode.dll:
non-ecma libs in /usr/lib/banshee-1/Extensions/Banshee.MultimediaKeys.dll:
non-ecma libs in /usr/lib/banshee-1/Extensions/Banshee.NotificationArea.dll:
non-ecma libs in /usr/lib/banshee-1/Extensions/Banshee.NowPlaying.dll:
non-ecma libs in /usr/lib/banshee-1/Extensions/Banshee.PlayQueue.dll:
non-ecma libs in /usr/lib/banshee-1/Extensions/Banshee.Podcasting.dll:
Name=System.Web
non-ecma libs in /usr/lib/banshee-1/Extensions/ipod-sharp.dll:
non-ecma libs in /usr/lib/banshee-1/Extensions/ipod-sharp-ui.dll:
jms@osc-franzibald:~$ for i in /usr/lib/gnome-do/*.exe /usr/lib/gnome-do/*.dll /usr/lib/gnome-do/plugins/*.dll; do echo non-ecma libs in $i:; monodis –assemblyref $i | grep System | grep -v System$ | grep -v System.Xml$; done
non-ecma libs in /usr/lib/gnome-do/Do.exe:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/Do.Interface.Linux.AnimationBase.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/Do.Interface.Linux.Classic.dll:
non-ecma libs in /usr/lib/gnome-do/Do.Interface.Linux.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/Do.Interface.Linux.Docky.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/Do.Interface.Linux.GlassFrame.dll:
non-ecma libs in /usr/lib/gnome-do/Do.Interface.Linux.HUD.dll:
non-ecma libs in /usr/lib/gnome-do/Do.Interface.Linux.Mini.dll:
non-ecma libs in /usr/lib/gnome-do/Do.Interface.Wink.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/Do.Platform.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/Do.Platform.Linux.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/Do.Universe.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/Alias.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/AptURL.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/Archive.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/Banshee.CollectionIndexer.dll:
non-ecma libs in /usr/lib/gnome-do/plugins/Banshee.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/BatteryMonitor.dll:
non-ecma libs in /usr/lib/gnome-do/plugins/Bibtex.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/ClawsMail.dll:
non-ecma libs in /usr/lib/gnome-do/plugins/Cl.ickable.dll:
Name=System.Web
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/Confluence.dll:
Name=System.Core
Name=System.Web.Services
non-ecma libs in /usr/lib/gnome-do/plugins/CPUMonitorDocklet.dll:
non-ecma libs in /usr/lib/gnome-do/plugins/del.icio.us.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/DiskMounter.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/Dropbox.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/Emesene.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/EOG-Slideshow.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/Epiphany.dll:
non-ecma libs in /usr/lib/gnome-do/plugins/Evolution.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/Exaile.dll:
Name=System.Core
Name=System.Data
non-ecma libs in /usr/lib/gnome-do/plugins/File.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/Firefox.dll:
Name=System.Core
Name=System.Data
non-ecma libs in /usr/lib/gnome-do/plugins/Flickr.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/GNOME-Dictionary.dll:
non-ecma libs in /usr/lib/gnome-do/plugins/GNOME-Screenshot.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/GNOME-Session.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/GNOME-Terminal.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/GoogleCalculator.dll:
Name=System.Web
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/GoogleCalendar.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/GoogleContacts.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/GoogleDocs.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/GoogleMaps.dll:
Name=System.Core
Name=System.Web
non-ecma libs in /usr/lib/gnome-do/plugins/GoogleSearch.dll:
Name=System.Web
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/ImageShack.dll:
Name=System.Core
Name=System.Xml.Linq
non-ecma libs in /usr/lib/gnome-do/plugins/JIRA.dll:
Name=System.Web.Services
non-ecma libs in /usr/lib/gnome-do/plugins/Launchpad.dll:
Name=System.Core
Name=System.Web
non-ecma libs in /usr/lib/gnome-do/plugins/LocateFiles.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/ManLookUp.dll:
non-ecma libs in /usr/lib/gnome-do/plugins/Microblog.dll:
Name=System.Core
Name=System.Web
non-ecma libs in /usr/lib/gnome-do/plugins/MPD.dll:
non-ecma libs in /usr/lib/gnome-do/plugins/NX.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/OpenSearch.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/Opera.dll:
non-ecma libs in /usr/lib/gnome-do/plugins/Pastebin.dll:
Name=System.Core
Name=System.Web
non-ecma libs in /usr/lib/gnome-do/plugins/Pidgin.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/PingFM.dll:
Name=System.Web
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/Putty.dll:
Name=System.Web
non-ecma libs in /usr/lib/gnome-do/plugins/Quote.dll:
Name=System.Web
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/RemindMe.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/RequestTracker.dll:
Name=System.Core
Name=System.Web
non-ecma libs in /usr/lib/gnome-do/plugins/Rhythmbox.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/Riptide.dll:
Name=System.Core
Name=System.Web
non-ecma libs in /usr/lib/gnome-do/plugins/RSS.dll:
Name=System.Core
Name=System.Web
non-ecma libs in /usr/lib/gnome-do/plugins/RTM.dll:
Name=System.Core
Name=System.Web
non-ecma libs in /usr/lib/gnome-do/plugins/Shelf.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/Skype.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/SqueezeCenter.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/SSH.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/StockQuote.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/SwitcherDocklet.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/SystemServices.dll:
non-ecma libs in /usr/lib/gnome-do/plugins/Tasque.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/TerminalServerClient.dll:
non-ecma libs in /usr/lib/gnome-do/plugins/Text.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/Thunderbird.dll:
non-ecma libs in /usr/lib/gnome-do/plugins/TinyUrl.dll:
Name=System.Web
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/Tomboy.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/TrackerSearch.dll:
non-ecma libs in /usr/lib/gnome-do/plugins/Translate.dll:
Name=System.Core
Name=System.Web
non-ecma libs in /usr/lib/gnome-do/plugins/Vinagre.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/VirtualBox.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/VolumeControl.dll:
non-ecma libs in /usr/lib/gnome-do/plugins/VolumeDocklet.dll:
non-ecma libs in /usr/lib/gnome-do/plugins/WeatherDocklet.dll:
Name=System.Core
Name=System.Web
non-ecma libs in /usr/lib/gnome-do/plugins/WindowManager.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/Woof.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/Wordnet.dll:
non-ecma libs in /usr/lib/gnome-do/plugins/xmms2.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/YouTube.dll:
Name=System.Core
non-ecma libs in /usr/lib/gnome-do/plugins/Zim.dll:
Name=System.Core
I really doubt there’s anything patentable in System.Web (it’s trivial stuff for mail & web interaction). System.Data is indeed the “scary” ADO.NET, which is .NET speak for “JDBC”, but all concerned are happy to stop using that abstraction once they know what exactly they need to stop using and start using instead. System.Core relates to C# 3.0 (which Do uses heavily), but I SINCERELY doubt that it’s not going to be on the table right now, as the ECMA (currently) debates 334/335 version 5.
#9 by Jo Shields on July 24th, 2009
In case it wasn’t obvious, the “non-ECMA” libraries are any whose name starts with “System”, other than System or System.Xml
#10 by Jo Shields on July 24th, 2009
Perhaps. I suspect the political climate would take any decision out of my hands, really. But, again, there’s the issue of the size of the company – The stuff I work with is a “clone” of something from Developer Tools, (unquestionably) the most FOSS-friendly end of the company. And, not to put too fine a point on it, but as we approach the flying-cars future of 2010, I think Developer Tools know full well that any attempt to kill Mono would seriously harm THEIR profitability by irreparably damaging their standing amongst the too-big-to-ignore-even-thought-they-want-to Open Source crowd. (Just as any attack against Moonlight, even on non-protected distros, would seriously harm their ability to compete with Adobe and theirfore their profitability). I don’t think releasing, say, IronPython or IronRuby under a Free license is altruism – it’s late-00’s customer demand.
So can “Microsoft” reach that point? Perhaps – but I just find it so difficult to approach a behemoth their size with a single viewpoint. My favourite comparison at this point is Sony. Sony are responsible for putting rootkits on “Audio” CD’s – and are also responsible for making the PS3 the first major home console with Linux support out of the box. Are Sony good, or are Sony evil? Perhaps they’re both, in a state of constant flux, whose status is only determined upon observation.
#11 by Jo Shields on July 24th, 2009
Here’s the other funny thing – the guy who wrote that came into #mono, asked him for help researching his question, and was specifically taught about the difference between Using versus -r:foo.dll, as well as the command to find the real dependencies of an app
The next post on his blog shows some excerpts: http://rofrol.wordpress.com/2009/07/23/tomboy-once-again/
Although he seems to have incorrectly turned my “mscorlib” into “mscorelib”
#12 by Jo Shields on July 24th, 2009
And he’s been observed getting “research” from #boycottnovell. Sigh.
See the problem now, Jason? All roads lead to Roy. As long as serial liars set the talking points, there’s no end to this – and all critics end up bundled together with Roy, because chances are, that’s where they belong
#13 by Jason on July 24th, 2009
@Jo,
I concede that point to you, sir.
I confess I did not realize the extent of it until I tried taking a different tact here.
#14 by theodor on July 24th, 2009
Another emotional point.
I think it’s reasonable to dislike Microsoft. I also think it’s somewhat illogical NOT to dislike Microsoft unless you’re on their payroll or benefiting in some other way from them. You know how history teaches.
So… probably I’m in a tiny minority but my emotional problem is: I don’t want to be running .exes and .dlls on my Linux install. Not by default.
Dropping these conventions would go a long way in making me like Mono.
Sure it would break the standard and require a lot of work for a “silly” reason and I also don’t want to tell other people how to do their work or what framework to use.
I simply dislike the current convention.
#15 by Jo Shields on July 24th, 2009
Just the file extensions, or the full PE header block? Just to make it plain, ECMA335 mandates PE.
#16 by Jason on July 24th, 2009
@theodor,
Heh. I recall someone else bringing that up (on Ubuntu Forums?) they didn’t like “.exe” and I think it was actually Mr. Shields who pointed out the extensions aren’t actually needed.
Weird that I remember that. I can’t believe my head is filling with Mono trivia.
#17 by Jo Shields on July 24th, 2009
jms@osc-franzibald:/tmp$ gmcs hello.cs
jms@osc-franzibald:/tmp$ mv hello.exe hello.panda
jms@osc-franzibald:/tmp$ mono hello.panda
Hello, World!
Problems begin to appear in the case of library references, though. Especially in the GAC.
#18 by theodor on July 24th, 2009
The extensions bother me more since they are much more visible. To a user that is.
And dropping the Windows header would get us back to completely recompiling/relinking for every platform wouldn’t it?
That’s clearly contraproductive… so I’d settle for the extensions
#19 by zekopeko on July 24th, 2009
How are they visible to the user? Even under Windows the extension are hidden by default.
I click on a shortcut in/on my Start menu/Desktop not directly on the .exe file.
The same way I do it in Linux. Even from the command line I can start applications with typing the name under which it exists in my $PATH. I don’t type /usr/bin/Banshee.exe (since it doesn’t exist as such in the bin folder) but /usr/bin/banshee since it’s simply a shortcut that calls the binary with various switches.
Don’t create an issue from a non issue.
Disclaimer: I’m not on a Linux box so path’s are completely made-up.
#20 by Jo Shields on July 24th, 2009
Comments with more than X links are moderated, where X is i-have-no-idea
#21 by Jason on July 24th, 2009
X=2 by default (and is current setting)
#22 by zekopeko on July 24th, 2009
Yeah, I figured that out. At first I was thinking that Google Chrome is acting up, since I’m using an unstable version.
#23 by Jo Shields on July 24th, 2009
/usr/lib/banshee-1/Banshee.exe
Good guess though.
And generally speaking you’d only notice the extensions when looking through “ps” output (gnome system monitor doesn’t show extensions), and if you use things like “locate”
It’s a small issue – but I image a “fix” would be small too, to support more than one extension.
#24 by Nobody Reeal on July 25th, 2009
I think Jo goes a long way to show you that many of your assumptions are, in fact, based on either incorrect information or deliberate misinformation.
It would go a long way towards true objectivity to veryify your assumptions are true first.
However, let’s address some of your points.
“MIcrosoft Joins the OIN”
While that would be wonderful, I have to ask.. What’s in it for them? OIN is about protectecting other open source providers, not commercial vendors. If Microsoft joined OIN it would be a one-way street. Others would get the benefits of MS’s patents, but MS would be unable to get the benefits of the OIN. The OIN License only applies to Linux systems, and that’s quite specific.
Microsoft would be unable to take advantage of OIN’s patent pool in Windows because Windows is not Linux.
So I really see no benefit for Microsoft to join OIN, even if they would be happy to share their patents with Open source on a quid pro quo basis.
“Microsoft talks openly and honestly about Linux”
It might help your argument if so many Linux advocates weren’t guilty of this themselves. You seem more open and willing to discuss things than others, but the fact of the matter is that you seem to be complicit with the amount of dishonesty that goes on about Microsoft. I don’t see you posting a single article that critically takes a Linux advocate to task for false information (and there are lots of examples that I’m sure even you know to be the case).
Not that you have to be the Linux truth enforcer, but one has to wonder if you’re so concerned about truth, why you don’t occasionally ding those that bend it on your own side?
So, all that being said, I think when both sides are open and honest, real change can happen.. but you know as I do that this isn’t likely to happen.
“Microsoft replaces Ballmer with someone non-psychopathic”
Ballmer certainly isn’t a good image for Microsoft. I can agree with that.
“Microsoft releases some interesting code, GPL style for bonus points”
Microsoft has released a lot of code under FSF recognized Free licenses. No, they’ve not released any of their primary products as such, but you wouldn’t expect them to.
Frankly, the only reason we have products like OpenOfficce and Symphony from big companies is because they see it as a tool to fight Microsoft. I guarantee you that if MS were to die next week, so too would IBM’s committment to Symphony and Sun’s committment to OpenOffice.
“Microsoft releases a linux distro”
I think that’s a bit much. Microsoft has no interest in creating Linux operating systems. Even IBM doesn’t have their own distro, so why would Microsoft be expected to release one to “prove” thier Linux committment?
“Time passes peacefully”
It’s hard for time to pass peacefully when there is an entire army of people dedicated to disturbing the peace. Don’t you think that, even if MS did absolutely nothing that anyone could legitimately fault them for that the anti-MS crowd would stand by idly? No. They already invent stuff, nothing would stop them.
On Mono:
“A Credible Endorsement”
Considering that Red Hat, Ubuntu, and other major players don’t see a problem with Mono, how would that not be credible endorsements?
How’s this for credible? You use RMS as a credible source against Mono. RMS recently just chastized the Swedish Pirate Party for wanting to reduce copyrights to 5 years. RMS complained that this would defeat the purpose of the copyleft. RMS wants copyrights to exist, and for as long as possible, because it’s the only way to compel people to release their source code.
In other words, RMS is his own worst enemy sometimes, and his agenda is usually counter to what normal everyday people would like.
I’m not going to go on.. but I guess my entire point is simply that you can’t reasonably expect a company, any company, to wholesale give up their rights, at least without some kind of concrete benefit to their shareholders. They’d be sued by their shareholders in an instant.
What’s more, most anti-MS proponents have highly unreasonable demands on what would appease them, such as Microsoft going completely open source. Not going to happen.
Certainly, Microsoft hasn’t put its best foot forward in regards to open source, but the fact is, actions speak louder than words… and to date, Microsoft hasn’t taken a single action directly against Open Source.
One can make arguments about SCO and TomTom, but the facts are, even if all the claims are true (and certainly some are true, but many of them are little more than speculation and circumstantial allegations…) they constitute Microsoft taking steps against commercial competitors, not Linux itself.
Frankly, until I see some real, hard evidence of Microsoft actually trying to destroy Linux or Open source, and not just grandstanding… I’ll take it with a huge grain of salt.
#25 by Robert Millan on July 25th, 2009
Nice list, Jason. A bunch of those would definitely convince me too, specially the OIN one.
But what would really make me change my mind is a change in attitude. I had a lot of expectations when I saw Miguel advocating for splitting “covered” from “non-covered” components. I thought that a bigger change might follow, in such a way that:
– The patent-encumbered part of what Mono is today becomes a compatibility project with similar aim as Wine.
– The part we want as a framework for free applications is entirely based on code that is covered by a patent promise, and further APIs are developed/designed by the community.
Today, we have e.g. Windows.Forms and GTK# as canonical representatives of each category, but the line dividing them is blurred.
#26 by tacone on July 25th, 2009
Robert: also there’s some push to make banshee use even more legally-obscure technologies, namely Moonlight.
Banshee is the umbrella project of the Mono project, it means that Mono followed Banshee needs to some extent.
I’m pretty happy with Miguel’s mono packages split. Still, the dark packages
are needed for banshee (and f-spot as it will be re-implemented on top of Banshee).
I personally don’t need MS to join the OIN (it would be seen as an infiltration by many people btw), I just need a better patent covenant.
Miguel stated on this blog that they’re working with MS to obtain that (and for Moonlight as well). I’m not positive it will happen soon, but sure I hope it will.
#27 by zekopeko on July 25th, 2009
mmmm… this is how things are now. What’s your point?
Not on my Ubuntu install. Windows.Forms is a completely separate package. Miguel said that they will separate the code in the Mono SVN so that it’s easier for distros to pick and choose what they want (and I think that they were planning to do it even before; <-take with a huge grain of salt).
#28 by zekopeko on July 25th, 2009
How is Banshee an umbrella project? I’m not following. Are you suggesting that Moonlight is going to be part of Mono? If so, (AFAIK) it’s only a mini platform built on Mono.
I’m guessing that you are referring to ADO.NET, since I don’t know of any other “dark package” that Banshee uses. AFAIK ADO.NET is only an interface for communicating with databases. If that is a problem for Mono I’m left wondering what are the consequences for other FLOSS platforms that implement similar functionality.
Only the paranoid would see this as an infiltration. It would only benefit MS and FLOSS.
FLOSS wouldn’t have to worry about MS (and would have their patent portfolio for added defense) and vice versa. This would only be a good thing. And I have no doubt in my mind that OIN lawyers would vet the agreement thoroughly.
#29 by Jason on July 25th, 2009
@Nobody Real
What? What assumptions are incorrect or deliberate misinformation. Be specific and explicit, please.
If you want to come on here and call me a liar, fine. But please break it down so I can at least defend myself.
Thanks much.
Uh, because the OIN would obviously change structure to reciprocate protections to Microsoft. This is so obvious that I have a hard time believing you couldn’t connect these dots.
The name of this blog isn’t “Linux Liars”, so I’m not going to post on that, anymore than I am going to post fried chicken recipies or great snowboarding destinations.
I have “dinged” lies and questionable characters in the comments when specifically mentioned. I certainly do not link or use “questionable” sources.
This is just a list of possible things that would each go a some way to changing my mind. Not a single one is necessary or sufficient. I said that at the start of the thing.
I don’t think it is very realistic or likely either. But if it happened, it would move my opinion.
Some people would remain anti-Microsoft no matter what, sure. But that number is a very small amount.
Most people that oppose Microsoft are not fanatical Microsoft haters, they just have experience. Once a new experience (Microsoft being good) overcomes the bad experience (Microsoft being bad), they will change.
This is a fair point and well-stated. More endorsements never hurt, that is my point, not that Mono has none
Let’s just say I disagree with your characterization of RMS’ argument here.
No. Most “anti-Microsoft proponents” do not call for Microsoft to go completely Open Source. I certainly have never made such a call, not even in this “wish list” here.
Um. All I can say is that if you think “to date” Microsoft hasn’t taken a single action directly against Open Source, you are woefully misinformed.
I guess you could start with “Microsoft: A History of Anticompetitive Behavior and Consumer Harm” (PDF), or just read what Microsoft themself have to say on the matter: MS and FLOSS.
I understand (but disagree) with the argument that things aren’t don’t that way anymore at Microsoft, but to flatly state that “to date Microsoft hasn’t take a single action directly against Open Source” is just not factual.
#30 by Nobody Reeal on July 25th, 2009
Well, I had a very long rebuttal typed out here, but lost it due to clicking on one of your links rather than opening a new tab. Gah.
So I’ll start again.
No, I did not call you a liar. That should be abundantly plain by my words, but apparently not. So let me be more clear.
I said “It would go a long way towards true objectivity to veryify your assumptions are true first.”
I said your assumptions were based on incorrect information or deliberate misinformation. I did not say that what you wrote was deliberate misinformation. How is that difficult to understand?
There is a very old saying in the computer industry: GIGO. Garbage In, Garbage out. If your assumptions are incorrect, then so too will be your conclusions.
As an example of a recent false assumption, you wrote recently about how Microsoft’s release of GPL’d drivers was “ruined” because it was due to a GPL violation. Well, it turns out those reports were false and your assumptions were incorrect, thus your conclusions were incorrect.
In reality, the Vyatta engineer discovered that Microsoft had marked it’s exported interfaces as EXPORT_GPL_SYMBOL, which indicated to the kernel that it could only be used with GPL’d software. This was in contradiction to the proprietary nature of the DLL’s, and thus caused a licensing contradiction. Microsoft was not distributing any GPL’d code in violation of the license, they simply incorrectly told the kernel that you could only link the proprietary driver with GPL code.
Microsoft could have solved the problem in one of two ways, relink the code with the correct export markings, or release the code under the GPL. They chose the latter, and should be commended for doing so when they didn’t have to. Instead, you and others, based on false assumptions, spread even more false conclusions.
See my point?
Regarind the OIN:
“Uh, because the OIN would obviously change structure to reciprocate protections to Microsoft. This is so obvious that I have a hard time believing you couldn’t connect these dots.”
I don’t see how that conclusion is either obvious, or even likely. I think it highly UNlikely the OIN would restructure themselves like that, plus it would almost certainly stir up a huge controversy by the same people criticizing the novell deals (which I believe includes you).
The point being, Microsoft is not the one to decide that, even if it were willing.
Regarding criticizing the anti-MS camp, my point was not that you should write long missives criticizing Linux advocates, but rather that perhaps you show that you have your own opinions that differ in some way from the talking points going around, especially when such talking points aren’t always true (The FSF’s claims of non-ecma libraries in use by TomBoy for instance).
Regarding unreasonable demands, I did not say that most anti-microsoft proponents demand that MS go all open source. I merely included it as a demand that some have, however pointing out that most have unreasonable demands (you have a few yourself).
Regarding MS taking direct action against Open Source, you aren’t really rebutting anything I said. I said “Actions speak louder than words”. Comments made do not constitute direct action.
The fact of the matter is, Microsoft has not, and I do not believe they ever will take any direct action against Open Source. Doing so would be pointless, and expensive, and achieve no benefits and would create even more enemies.
I say its pointless because there’s nobody to sue, and even if you find someone they won’t have any money. That means the only thing you can achieve is to get them to stop doing whatever it is, which they will do the instant you issue a cease and desist.
In fact, it would be beneficial to Linux for Microsoft to issue cease and desists so that any such areas could be identified and fixed.
To be clear, I don’t consider vague comments to reporters to be “direct action”.
#31 by Nobody Reeal on July 25th, 2009
By the way, that ConsumerChoicePaper.pdf is… wow… There’s so much speculation in that masquerading as fact, I could spend a day writing a rebuttal and still not come close to addressing everything.
Certainly all the facts are correct (at least those that are cited), but he draws some very questionable conclusions from them.
Here’s an example:
He makes the insinuation that Microsoft didn’t release an OS between 2001 and 2007 because they were resting on their laurels with no competition, and when they did release an OS it was only half-hearted.
This falls in the face of the known facts. Microsoft spent an ungodly amount of money developing Vista, and in fact ended up throwing most of it away and starting over due to a variety of reasons, none of them anti-trust related.
In another section he claims this:
“While Microsoft eventually made changes to its conduct in each of these instances, these
incidents all demonstrate Microsoft’s willingness to use its monopoly products aggressively first
and make changes later only when confronted about its behavior.”
This ignores the simple fact that anti-trust law is not a clear-cut case of rules you can and can’t do. Each behavior has to be evaluated by a regulator to decide if it’s anti-competitive or not. In fact, a monopolist is the last person to have an objective view on how his actions are or are not anti-compative. Microsoft can’t sneeze without someone claiming they’re being opressed (a certain monty python skit comes to mind).
Certainly the paper presents some interesting arguments, but it’s couched in such hyperbole and grandstanding as to make it all but worthless if you are interested in an objective view.
#32 by Dan Serban on July 25th, 2009
@Nobody Reeal
Hmmm, it seems that unbeknownst to me and other people, Red Hat made a statement that they don’t object to Mono. Care to provide a reference? Care to also mention which other major players you mean? (Novell doesn’t count, before you put it on the list.)
Not everybody regards an endorsement by the Ubuntu Technical Board as credible. I certainly don’t.
#33 by Jason on July 25th, 2009
@Nobody Reeal
There is so much I disagree with, the original responses are much too long. I have tried to keep this short.
Exactly what are you criticizing? The fact that I can’t see the future? Everything I wrote was current information at the time of the writing.
And, in point of fact, I said “now it turns out it might be something they had to do”, which I think is perfectly fine given the stories that were going around. I haven’t written anything about it since the latest round of stories.
Let me just end this by saying I don’t think this is fair criticism.
Seriously. WTF is there to argue about? It is a “wish list”, not demands. Do you not understand the point of my post? And then you wave a touch of hypocrisy there at the end? What the hell?
Let me just end this by saying I don’t think this is fair criticism.
I don’t think I have once asserted that Tomboy uses non-ECMA libraries.
Are you suggesting I write an article like “Here is what some people think, but I don’t?” Who the hell writes that sort of article? No one, that’s who. How about I just write articles saying “Here is what I think”, instead?
Let me take a moment to say this clearly, because it is on the About page, but maybe people didn’t see it:
I welcome guest posts and contributions. I will post up a well-argued and well-written pro-mono article in a heartbeat. I have pretty relaxed editorial standards, meet them and the floor is yours.
Let me just end this by saying I don’t think this is fair criticism.
This is so out of alignment with what I consider reality, I can only assume you have defined “direct action” in such a restrictive manner that it excludes anything short of gun fire or ninja assassin squads.
I consider FUD, ad campaigns, public speeches, political lobbying, strong-arming other companies, bribing officials, stacking standards committees, threatening court action, funding third-party court actions, and so forth as direct actions.
I assume we will just have to disagree on this point.
Oh well, I thank you for your comments nonetheless.
#34 by vexorian on July 25th, 2009
To paraphrase Miguel de Icaza, I think you have spent too much time in your “love shield”.
#35 by Nobody Reeal on July 26th, 2009
Jason, why do you have such a hard time commenting on what I have said, rather than what you seem to want me to have said? You continually jump to conclusions that do not reflect what I have said. It’s no wonder you do it all the time in your writings.
“Exactly what are you criticizing? The fact that I can’t see the future? Everything I wrote was current information at the time of the writing.”
No, the fact that you didn’t verify your assumptions. Obviously it was not the current information because it was wrong. It was only misinformation being spread by people who also didn’t verify the facts. All it would have taken you was to contact the source, who seems more than willing to clarify the situation.
I realize you consider yourself an “opinionist” rather than a “journalist” but opinions should be founded on facts as well.
I only bring this up because you make yourself out to be an objective person with rational critical thinking. Except that you taint your reason with false assumptions.
“now it turns out it might be something they had to do because of a possible GPL violation”
Actually, this is what you said:
“Except now it turns out it might be something they had to do because of a possible GPL violation. Which poops all over the whole thing.”
If reread this statement, you see that you are rejecting it from your argument for what “may” be true. “Which poops all over the whole thing” is not “Which if true, would poop all over the thing”.
You reject it based on what might be, and that’s part of the issue with your rights. You make your judgements based on what “might” be, or at least some of the ones you write about.
“Seriously. WTF is there to argue about? It is a “wish list”, not demands.”
You say “What would it take to make me change my mind”. Then claim it’s a “wish list”. What is a demand? Dictionary.com defines one meaning as “to call for or require as just, proper, or necessary”, which I think fits your “what would it take?”.
“Demand” doesn’t mean “We demand MS do this”, it means “In order for us to not hate MS, they must meet our requirements”.
“I don’t think I have once asserted that Tomboy uses non-ECMA libraries.”
Again, you are responding to what you want me to have said. I did not say you did. I said, you did show any crticism of or difference of opinion when it comes to anti-Microsoft claims, such as the claims about TomBoy.
You might find you have better arguments if you listen to what people say and respond to what is said, not what you assume they must have said.
“This is so out of alignment with what I consider reality, I can only assume you have defined “direct action” in such a restrictive manner that it excludes anything short of gun fire or ninja assassin squads. ”
No, I consider “direct action” to be filing a cease and desist or filing a lawsuit. The theatrics don’t help.
Talk is cheap. And certainly the anti-Microsoft crowd has lots of their own talk, much of which is just as crazy as you accuse MS’s of being.
#36 by Nobody Reeal on July 26th, 2009
By the way, Jason. There’s something else i’d like to point out. You probably won’t like this either.
You don’t seem to go back and print any kind of corrections on what you write. Example above with the GPL violation.
When your arguments DO turn out to be wrong, you don’t correct them. You might say something down in the comments, but IMO that’s not quite good enough because people will continue to use your articles in THEIR arguments and never go down and read the comments.
I think it would be responsible of you to go back and edit your articles with corrections when you discover that the information you presented was wrong. This prevents outdated information from being used in the echo chamber where it gets repeated ad nauseum until everyone believes it’s the truth.
No, I don’t expect you to go back through everything you’ve ever written, but making a committment to correct future information would be a great idea.
Like I said, i don’t expect you will though. Opinion columnists generally don’t think enough of their own work (“Hey, it’s only my opinion, not an encyclopedia”) to demand accuracy.
#37 by tacone on July 26th, 2009
refer to this slideshow (pdf)
I’m suggesting Banshee UI will be implemented in Moonlight.
I’m not an expert in what Banshee uses. Other than ADO there may be Linq or other stuff. I’ve been said Banshee uses not just the (now) safe packages, but didn’t checked myself.
I’ve suggested that paranoids may be around. So good or bad thing, that may not help to stop flames. Not that ISO wasn’t a respectable body before OOXML happenings, though.
#38 by Anonymous on July 26th, 2009
@Nobody Reel,
If Microsoft was distributing DLLs which were designed to link to GPL code and the licensing of those DLLs was not compatible with the GPL, then it should be considered copyright infringement (i.e., a derived work was being distributed without proper authorization from the copyright holder).
I do not know whether that is the situation, but it is how I interpret the quoted description (unless the MS DLLs were either not distributed, or distributed under GPL-compatible licensing). Personally, I am not that interested in ephemeral violations of the Free Software licensing, as long as things eventually get worked out in good faith.
#39 by Jo Shields on July 26th, 2009
Mishandling EXPORT_GPL_SYMBOL isn’t a license violation. It’s working around a technical limitation in the kernel (by “underhanded” means)
Essentially, there are two issues at play here
1) The GPL permits you to distribute GPL-licensed source alongside binary-only proprietary objects, and to compile them together – it expressly forbids distributing the resulting module after compiling. When people talk about a “GPL violation” this is usually what they mean (the last kernel GPL violation I fought was like this) – but Microsoft were unequivocally NOT doing it like that (take a look at the ISO at http://www.microsoft.com/downloads/details.aspx?FamilyID=AB7F4983-93C5-4A70-8C79-0642F0D59EC2 – there are .c files, makefiles, and .i686/.x86_64 binary objects, just like NVIDIA or ATI or Highpoint)
2) This topic is NOT a licensing issue – but it IS considered a violation of trust. In the kernel, you can mark a given symbol with EXPORT_GPL_SYMBOL, which basically says “you can only access this piece of code if you are also GPL”. It’s a way to prevent proprietary kernel modules from accessing sections of the kernel which are ringfenced as GPL-only for ideological reasons. As opposed to EXPORT_SYMBOL which makes something generally available. Microsoft labeled their module so it would identify itself as GPL, meaning it could access (and did access) GPL-only symbols, even though it was not, in fact, the case (and, indeed, they’re not the first people to do this). Hell, it was even technically true, to a very limited extent – the .c files are indeed GPL/BSD (but the kernel module, once compiled, is obviously not)
BOTH of the above points can be considered underhanded – but both points are completely defused now by the GPL release of the code.
#40 by Jason on July 26th, 2009
@Nobody Reeal:
Thank you for your comments. I think that’s sufficient back-and-forth, we will just have to disagree.
#41 by saulgoode on July 26th, 2009
Objects designed to link with GPL-licensed code are derived works, and this would be a separate issue than merely aggregating unrelated works in a collection. The GPL does not permit derived works to be distributed unless done so under the GPL.
EXPORT_SYMBOL_GPL does not alter the licensing terms of the kernel, which is GPL2 with the only exception being that “user programs that use kernel services by normal system calls” are not considered derived works. The export flag is a bookkeeping/debugging mechanism that effectively allows the kernel to avoid rejecting non-compliant modules outright. It does NOT mean that non-GPL-compatible modules are thus deemed compliant; merely that the kernel won’t refuse to load them. Just because the kernel is not proactive about enforcing the law, does not mean that the law is not applicable.
As I haven’t investigated the details of what code Microsoft originally distributed (if any) under what licensing terms; there may be other reasons that the MS code was not infringing — however, the specific demurrals presented here by Nobody Reel and Jo Shields are not valid defenses against GPL infringement.
#42 by saulgoode on July 26th, 2009
You started out by asserting that the FSF’s claims about Tomboy using non-ECMA MS technology can easily be shown to be wrong yet, correct me if I am misunderstanding, your above analysis shows Tomboy does use some System components falling outside of ECMA. Caveats aside as to whether patents exist which cover System.Web; how easily System.Data functionality might be replaced; or plans to have the standard incorporate more components in the future, I fail to see how you’ve shown the FSF claim to be wrong.
#43 by Jo Shields on July 26th, 2009
Learn to read, Saul.
directhex@desire:~$ for i in /usr/lib/tomboy/Tomboy.exe /usr/lib/tomboy/addins/*.dll; do echo non-ecma libs in $i:; monodis –assemblyref $i | grep System | grep -v System$ | grep -v System.Xml$; done
non-ecma libs in /usr/lib/tomboy/Tomboy.exe:
non-ecma libs in /usr/lib/tomboy/addins/Backlinks.dll:
non-ecma libs in /usr/lib/tomboy/addins/Bugzilla.dll:
non-ecma libs in /usr/lib/tomboy/addins/Evolution.dll:
non-ecma libs in /usr/lib/tomboy/addins/ExportToHtml.dll:
non-ecma libs in /usr/lib/tomboy/addins/FileSystemSyncService.dll:
non-ecma libs in /usr/lib/tomboy/addins/FixedWidth.dll:
non-ecma libs in /usr/lib/tomboy/addins/InsertTimestamp.dll:
non-ecma libs in /usr/lib/tomboy/addins/NoteOfTheDay.dll:
non-ecma libs in /usr/lib/tomboy/addins/PrintNotes.dll:
non-ecma libs in /usr/lib/tomboy/addins/SshSyncServiceAddin.dll:
non-ecma libs in /usr/lib/tomboy/addins/StickyNoteImport.dll:
non-ecma libs in /usr/lib/tomboy/addins/Tasque.Addin.dll:
non-ecma libs in /usr/lib/tomboy/addins/WebDavSyncService.dll:
#44 by Jo Shields on July 26th, 2009
Which the GPL/BSD dual-licensed shim using those symbols IS distributed under.
EXPORT_SYMBOL_GPL does not alter the licensing terms of the kernel, which is GPL2 with the only exception being that “user programs that use kernel services by normal system calls” are not considered derived works. The export flag is a bookkeeping/debugging mechanism that effectively allows the kernel to avoid rejecting non-compliant modules outright. It does NOT mean that non-GPL-compatible modules are thus deemed compliant; merely that the kernel won’t refuse to load them. Just because the kernel is not proactive about enforcing the law, does not mean that the law is not applicable.
As I haven’t investigated the details of what code Microsoft originally distributed (if any) under what licensing terms; there may be other reasons that the MS code was not infringing — however, the specific demurrals presented here by Nobody Reel and Jo Shields are not valid defenses against GPL infringement.
I posted the URL to the original (and still available) download. Take a peek yourself.
#45 by saulgoode on July 26th, 2009
Tomboy uses Tasque (but does not necessarily depend upon it), which depends upon System.Web, which is not part of the ECMA 335 specification yet is technology developed by Microsoft. It is fine that you hold the opinion that Microsoft does not hold any valid patents on System.Web technologies; but your opinion does not prove the FSF claim incorrect.
I applaud your efforts to provide separation between ECMA and non-ECMA Mono components in your Debian packages — and recognize that you were doing so even before upstream announced their own efforts along those lines. Nonetheless, you have not shown to be false the FSF claim that “there are several libraries that are included with Mono, and commonly used by applications like Tomboy, that are not required by the standard”.
#46 by saulgoode on July 26th, 2009
I am extremely skeptical that writing non-compliant works based on GPLed software (e.g., Linux kernel modules) somehow becomes compliant because of an intermediate GPL/BSD shim. Such shim modules may be acceptable if the driver was designed for use with non-Linux OSes (ala NDISwrapper and, perhaps, nVidia). But the issue is not the shim, it is the original target of driver code. If the code was designed to work in Linux kernel space, it should be considered a derivative work of the kernel. If the code was designed to work with Windows (or SunOS, or BSD,…) then it should not be considered a derived work — and the provision of a compliantly licensed shim shouldn’t alter this.
I did visit the download page, and found no evidence to indicate the nature of any “proprietary” code (I didn’t download any files to see what was included) — whether it was coded specifically for use in Linux kernel space or was just Windows-targeted code with a shim wrapper.
To be fair, I think accusations of license violations should not have been made without providing conclusive evidence and I concede that you may be right that Microsoft did not violate the GPL. I just feel that IF either assertion is to be made, it has to address deeper issues than the ones presented.
Regardless of whether they were obliged to do so or not, in this instance I am quite pleased with Microsoft’s release of their code licensed under the GPL.
#47 by zomg! on July 26th, 2009
Why is that a problem? Why does a person have to justify their rejection of ? What if, having been around a while, a person has come to the (rather rational) conclusion that certain words really are rather scary? And what if all the argument they need is to hear one of those scary trigger words? Why do you demand that they sit through your extended apologetics, when they’ve already come to their own conclusions long ago? Who are you to demand that they do so?
I don’t want Microsoft within 100 light years of any machine under my control. It’s just that simple. “Microsoft” is a scary trigger word that sets off alarm bells between my ears. You can belittle me as irrational all you like, but I know better. I was there when Microsoft installed those bells.
#48 by Jo Shields on July 27th, 2009
At least we agree on something, then!
#49 by SubSonica on July 28th, 2009
Things that would change my mind, and would help me to trust again Mono developers and proponents:
-Release Mono under the GPLv3
-Mono fans stop bashing the FSF and RMS and treating software freedom as something undesirable and different and separate from source openness, and they.stop pretending there is no problem with Microsoft corporation or justifying/dowplayinf their bad deeds and aggresive strategies.
-I would also like the Mono proponents be more vocal against software patents and the extension of software patentability to parts of the world free from this legal threat to FOSS, instead of just claiming that its just the way it is and that we should just accept the statu-quo.
-Novell goes back to the community fully discloses the MSFT-Novell deal’s terms and does not renew them after the agreement has expired -2011- (or better, declares it does not want to continue with it)
-Canonical (not Jo Shields) launches and keeps available a mono-free flavor of Ubuntu (just like it does with kubuntu and xubuntu)
#50 by Jo Shields on July 28th, 2009
No pleasing some people
#51 by Dan Serban on July 28th, 2009
I’m fine with Jo Shields releasing Mono-free ISO images, and I hope it becomes a tradition, and I also hope we do eventually also get the more interesting i386 respin.