-
Website
http://tirania.org/blog -
Original page
http://tirania.org/blog/archive/2009/Sep-10.html -
Subscribe
All Comments -
Community
-
Top Commenters
-
Max "WorldMaker" Battcher
7 comments · 1 points
-
psantosl
18 comments · 1 points
-
whitemice
8 comments · 1 points
-
barrkel
6 comments · 3 points
-
Ed Ropple
27 comments · 13 points
-
-
Popular Threads
-
C# Support for Tuples - Miguel de Icaza
1 day ago · 27 comments
-
C# String Interpolation - Miguel de Icaza
4 days ago · 62 comments
-
Nine Months Later: Mono 2.6 and MonoDevelop 2.2 - Miguel de Icaza
1 week ago · 46 comments
-
Releasing Moonlight 2, Roadmap to Moonlight 3 and 4 - Miguel de Icaza
1 week ago · 31 comments
-
New Moonlight Covenant has been posted - Miguel de Icaza
2 days ago · 6 comments
-
C# Support for Tuples - Miguel de Icaza
Also, the comparison with FSF does not really fit ;-)
more open source stuff on Windows -> more stuff on Windows can be ported to Linux
more open source stuff on Windows -> Better Windows/Linux interoperability
I'm sure there are plenty of other easy answers to your "how" question.
Anybody spinning the Codeplex Foundation as a negative thing for Linux needs to go for a walk and try thinking about it again.
All great points. I'm amazed by the inability of some in the open source community to understand the simple and obvious fact that everyone benefits from more contributions to open source regardless of the technology or platform the open source code is being developed with and on. I write about this at the MindTouch blog: http://www.mindtouch.com/blog/2009/09/13/codepl...
- I disagree on the quantity statement. Why "more" is necessarily better is not really clear. OSS has too many projects, even big and famous, without enough resources to go on, or without sufficient quality to compete with the "closed" alternative. It would be better to concentrate the efforts.
- I disagree with what you say about open source products being ported from windows to linux, the trend is opposite, and hard to invert, since the biggest number of users is on Windows anyway, especially for the desktop applications Linux desperately needs and not many (or nobody) is working on. Of course I would be happy to be contraddicted (with evidence) about this.
- Linux/Windows interoperability, as in all other cases involving different systems, is achieved using standard formats, and not necessarily using the same application, which is just another form of lock-in. Not much, in spite of the efforts has been done in this direction. A simple example is represented by the office formats interoperability. Microsoft released the specifications of legacy formats (.doc, .xls, ...) years ago, and OpenOffice is quite far from a complete sopport, since it is still unable to properly manage many relatively simple documents. The same can be said about OOXML, which is not fully supported even using the Novell OOXML converter (no proper management of embedded objects, and not always faithful conversions).
- More open source stuff may imply less closed source stuff, which *is* good. How many closed source projects, even big ones, die from lack of resources? What happens to its users then?
- Open source gives you the ability to port a project to Linux. Closed source? No chance.
- With open source, you can fix interoperability issues by implementing standard formats. With closed source you are left at the whims of the vendor. Think Skype.
- No. More open source stuff does not necessarily mean "less closed" stuff, since there are requirements to be met. In particular "open" is not enough to replace "closed" software, if the functionalities are not there. And this is a well known issue affecting many popular Linux applications, starting from OpenOffice. The usual reply "but it's enough for most users" is quite out of place due to the interoperability issues.
- Yes, open source gives you, in theory, the ability of porting an application to Linux. In practice, you need to think to that since the beginning, or the port becomes a huge effort if you start developing without thinking to a port in advance. In particular, porting from Windows to Linux is not as easy as porting from a UNIX flavour to another.
- Right, with open source you can, always in theory, implement standard formats. But at this time I'm not aware of any open source suite 100% compatible with OOXML or 100% compatible with MS legacy office formats, even if the specs are out there in the wild, to quote the same example I did before. Skype, on the other side, does quite a good job supporting all major platforms (Win/Mac/Lin). I don't think we can blame them if they choose to keep their code closed. It's a choice. My point has not been, since the beginning, against closed source software, but against moving open source software to a foundation led by a not exactly open source friendly and Linux friendly company, since this could not be positive for Linux as OS, and especially as desktop OS (which is something not many believe in, I guess).
I do not wish to derail this discussion any more, but you seem to be ignoring a simple fact: all three points you make affect closed source applications to a much larger extent than open source ones.
OpenOffice is not 100% compatible with OOXML. Guess what, MS Office is not 100% compatible either, but the difference is there's nothing you can do about it.
Skype does not do a "good job of supporting all major platforms". In fact, Skype/Linux is downright awful: it's still on version 2 when on windows it's on version 4; there's no amd64 support; fullscreen video behaves badly; it crashes a lot... The Skype protocol itself is completely closed, which means you cannot create a better client even if you wanted to.
You don't seem to have any problems with this, yet you are distrustful of Microsoft taking part in an open source effort.
Maybe it's just a different point of view, but I much prefer Microsoft becoming more open source friendly than staying on the other side of the fence forever. I distrust Skype much, *much* more, simply because they have shown no intention of ever playing well with others.
Mono and Moonlight are part of Novell efforts to improve the interoperability with MS products, and they were two examples of positive things.
I don't ignore the fact you cannot change closed source products. I simply say that this initiative is not going to help in the direction of bringing more open products of high quality to Linux. I never said anything else, since the beginning. Just check ;-)
[From here on, it is a reply to other points and it might be OT]
Skype, for your information, has a different numbering for Linux versions, and yes, it is behind with respect to the Windows version, but it is fully functional. The next release is going to support PulseAudio, enhanced video, a more efficient protocol and SMS. I live abroad for work and use Skype at least three times a day to keep in touch with friends and relatives, and I do not experience all these crashes. It is 32 bit, but modern distributions like SUSE manage that transparently. You are right on one point: it is closed, but it works, and it is what counts.
I'm not distrustful with Microsoft itself. Never said that. I said, and repeat, that I do not see the advantages of this initiative for *Linux* as an operating system, especially for the desktop, since the declared purpose of Microsoft is to have Windows as reference platform for the development of open source project (see, for example, the MS statements about making apache work on Windows).
I would *love* to have Microsoft really be more open, but frankly that's smoke in the eyes. Microsoft is doing this with one purpose, and it is not of becoming more open, but of keeping its market share. Is this wrong? No. Just do not push it as a friendly behaviour towards Linux. Take a look at how much effort Microsoft is putting in Linux, for example considering the effort they're putting in Hyper-V drivers, released to fix a licence issue. Even Greg K. H., who was proclaiming victory, had to complain about their lack of efforts.
In all this, Skype is a minor player. Microsoft is not. There is nothing wrong in keeping a protocol closed. Skype is not forcing you to use their products, while this cannot be said so clearly for Microsoft. You find Microsoft at school, at work, you depend on their technology to access to services of certain offices, banks and other online providers. Interoperability with them is not a choice, it is a requirement. As a consequence, the comparison just does not stay up.
[/OT]
Linux (and OS X) is only mentioned as an means to catch the attention of otherwise non interested community.
The true beneficiary is, of course, the platform, which if only had remained in its intended niche (Windows) would never acquired the critical mass of even become relevant for the industry to pay attention.
This is only good for .Net because it takes one step more in making the underlying OS irrelevant. As more people see that in a non distant future Operating Systems may very well go out of the game in computing (f.e. http://www.techflash.com/seattle/2009/08/VMware...) is critical to own an API for which one can reclaim some kind of tax or credit.
How ironic would it be, if an open minded, open standards, cooperative Microsoft helped to save us from the single hardware vendor / software vendor monopoly that Apple is trying to create.
Of course, GNU importance is undisputable. RMS is also one of the "founding fathers" of modern OSS, but I really think the GNU/Linux was completely pointless and unnecessary.
After reading what he did to Miguel, I thought: "My god, I was right, some guys at the open source community really have inflated egos and sometimes act like dictators".
These kind of guys are the ones that, despite what they say, really want that the community continues like some kind of "secret society", only selected members are allowed and they must obbey to their rules.
They have "enemies", like Microsoft, and acknowledging that the enemy has created something good is a "sin".
That'z why I love Mono: it is made by open-minded, non-radical, altruist people, who is humble enough to assume that yes, Microsoft and others made good things and can also "join the club".
Congratulations, Miguel, for you courage to stand for your opinions and for being open to new ideas. Being "fired" by RMS really made me admire you as a person even more (as a programmer, you got me way back there with mc and mcedit ;-)
But if you look at the history than you can see that there was never an attempt to rename Linux! Linus Torvalds developed a kernel which he called Linux. Both FSF and RMS always called Linux Linux. But before Linux they started to develop an operating system which they called GNU. GNU was almost done as Linux showed up. People combined Linux with GNU to get a complete operating system. Even if you are completely neutral than "Linux" is as OK as "GNU" for the operating system. An compromise which could make everyone happy and recognise every project could be "GNU/Linux". This was FSF's proposal. But whether you go for "Linux", "GNU" or "GNU/Linux" there is never something renamed!
The funny thing I recognise. That many people who are vocal about "FSF want to rename Linux to GNU/Linux" are the same people who have no conscience-smitten by renaming "Free Software" to "Open Source" which compared to "Linux vs GNU/Linux" is a real renaming.
GNU lost the PR war. Tough for them, but nobody else really cares. Maybe someone would care if the organization wasn't run by congenital pot-stirrers.
A name is an identifier. To the point that the word "Linux" serves as a properly unambiguous label, one should use it. Should there arise a situation where further specification is necessary, then and only then, would the elongated label be appropriate.
GNU is *implied*. Being pedantic about it ruins your ability to actually communicate with other people.
Many computer users run a modified version of the GNU system every day, without realizing it. Through a peculiar turn of events, the version of GNU which is widely used today is often called "Linux", and many of its users are not aware that it is basically the GNU system, developed by the GNU Project.
There really is a Linux, and these people are using it, but it is just a part of the system they use. Linux is the kernel: the program in the system that allocates the machine's resources to the other programs that you run. The kernel is an essential part of an operating system, but useless by itself; it can only function in the context of a complete operating system. Linux is normally used in combination with the GNU operating system: the whole system is basically GNU with Linux added, or GNU/Linux. All the so-called "Linux" distributions are really distributions of GNU/Linux.
Users like to call this OS "Linux" not "GNU slash Linux (tm)". Just like they prefer to say "Windows" rather than "Microsoft Windows Vista Enterprise Edition with Service Pack 3 (tm x 3)".
Besides, Linux is simply more catchy than GNU/Linux.
I can see how this can be annoying for those who work on GNU but the hard truth is that noone else cares. In other words, use GNU/Linux all you like in marketing material or technical discussions but the users have the final word on how they are going to call it. They do not mean this as some subtle attack against GNU - it's simply how things work.
EDIT: http://www.gnu.org/gnu/linux-and-gnu.html
Afterall, who is helping Free Software more than Microsoft? I can't think of anyone!
Way to go Miguel! ;)
I don't think either of us are "looking forward to" that event.
So when you say FOSS community you actually mean GPL comunity, but the later is just a subset of the much larger OS community.
I don't want to start a religious war, but OS as a concept of having the source and ability to modify it, it's much much more important than GPL will ever be.
ah well, I just wanted to pop in and say a big congratulations! I think its a wonderful opportunity and a nice gesture. And the anecdote about the FSF was priceless and made me laugh horribly :)
I am not sure exactly what you find so outrageous, and why you found the need to use double admiration marks. Perhaps I can explain. Since I work in Mono and Moonlight there are significant technological touch points with Microsoft; If I worked on say an open source Flash player or a PDF renderer, I would engage Adobe more; If I worked on device drivers for the kernel, I would be engaging the OEM and hardware community.
As for working for Microsoft as a replacement for Sam Ramji, I can see why you think I should work there or take that job. I have been trying to bridge the open source world and Microsoft for a long time, discussing and engaging with folks at Microsoft and in our community to find consensus and areas of collaboration. Many years ago I learned that you can achieve more by engaging other people than by insulting or attacking. In general, Outrage is not a very sophisticated human trait, it is rather primitive. You might want to look into that.
But I do that as a side thing. My real passion is writing software, and in particular software that helps Linux become better. This is where Mono and Moonlight came from: from the desire of bringing a great technology to Linux. And as a programmer, I rather continue to work writing software and working with the fantastic Mono team at Novell and the Mono community to improve Mono, improve Linux and improve open source than work as a bridge-builder at Microsoft.
Miguel.
You are entitled to your own views...and so am I entitled to mine. Your intentions seem to be more at creating fissures than uniting any community. In your position, you are able to make crucial decisions regarding technology and thus have chosen Microsoft's .NET for Mono. I too, in my area (yes I am a corporate Opensuse user)...I am disassociating from Opensuse GNOME and Novell forever.
I may be a small fry compared to a heavy hitter like you who has done a lot of work...but I will influence decisions that I can take.
I think you'll find that most of your customers (that you influence with your technology decisions) will not share your fundamentalist view as they normally only care about using the best-technology for the job that provides the most value with the lowest cost, so in this regard you are doing them a disservice.
I personally choose to use C#/VS.NET+ReSharper for most of my server-side development because after evaluating a lot of languages and frameworks in the past (C++ / PHP / Python / Java) it is the one that makes me the most productive and by extension gives my employer the most value.
Mono has basically given the software I produce 'extra value' because now the software I write can be deployed on a host of Operating Systems, which is fantastic as I believe that Linux is the best deployment platform taking into consideration 'cost / remote administration / etc'.
I am not a fundamentalist. Its funny how easy it is to label someone as that, even when I'd agree to disagree with Miguel on his choices. Neither you nor Miguel can convince me otherwise. Heck, if you did try to (and you're trying to), it makes you a fundamentalist too.
I'm not trying to convince anyone of anything, I'm only stating my opinions as well that *I* chose the 'best tools for the job for me' based on the best technology available. Other people may not come to the same conclusion and prefer 'Java / python / C' which is totally fine as well.
I also believe that open-source is the best model for software development as well and that Mono is a valuable contribution to Linux/OSS as it allows for software that previously would only run on Windows/.NET to run on Linux/Mono. As a prime example applications based on my open-source webservices stack (http://www.servicestack.net/) now have the opportunity (and do) run on Linux.
Honestly, it's this kind or blind hate and infighting that makes me think Linux has no chance at being more than a minor platform. How can humanity trust Linux with a significant market share, if you guy act like 2 year olds every time you don't like something. Grow the hell up.
The following is a repost from a discussion earlier this year, I am pasting it because it describes my position:
-----------------------------------------
[...]
What I believe is happening is that at the core, you are anti-
Microsoft and you do want to fight anything that comes from them.
[...]
I read this story on Ben's book. A shoe company sends two salesmen
to a rural area in Africa, and after a couple of weeks, he receives a
telegram from one of his sales people, it reads "ABORT MISSION, NOBODY
HERE WEARS SHOES, GOING BACK HOME". Then he receives a message from
the other sales man and it reads "GREAT BUSINESS OPPORTUNITY, NOBODY
HERE HAS SHOES. SIGNED LEASE FOR STORE".
I like the second world, the world of possibility. A world where we
can help Microsoft become a better open source citizen. I see a world
where we can grow the pie, instead of a world where we have to divide
the pie, where hackers at every company share knowledge and code.
When your world is a world of hate, fear and impossibilities you give
up early.
But currently the info page is full of pretty words trying to make Microsoft look good to the community but lacks any kind of commitment and substance. Codeplex as is is just a bunch of small java script proof-of-concept projects for Internet Explorer.. What will change this time around?
Microsoft encouraging open source > Microsoft discouraging open source
Yes, it would be nice if they freed their own software, and it's good to encourage them to do so, but that doesn't make the big step they're making with the Codeplex Foundation somehow insignificant.
MS is NOTHING if not a consumate marking firm and master corporate raider. They will find a way to use and abuse the opensource community model ( stroking individual developers to create an illusion of softness), meanwhile hiding opensource from the general consumer with its consumate skills of obfuscation, deflection and misdirection.
This kind of behavior reminds me of a serial abuser, trashing their victim, then feigning repentance with a token olive branch, then a new beating, then mock remorse, then another choking, then a crying jag....lather, rinse, repeat.
I was worried when I saw your name there because I immediately thought that the negative thinkers would tear you apart. Kudos for not worrying about them.
I am cautiously optimistic about this. Hopefully this won't be a complete perversion of the spirit of open source software...
The sad thing I see from many people is a bizarre desire for Microsoft to go and create its own, competing open source ecosystem detached from all our GNU stuff. That is not the way forwards; it flies right in the face of the openness and sharing that happens to be our biggest strength. Microsoft isn't going anywhere, so we can either try to get them speaking our language or create a huge mess for our end users.
Hostile competition would KILL open source, and the only way to avoid that is being open with all parties involved, including Microsoft.
You know, your entry would have stood on its own without this last part. All you do by making gratuitous jabs like this is cement the opinions of your detractors and give them fuel with which to burn their fires, and you make some of us wonder if, maybe, they aren't entirely insane and maybe they have at least something resembling a point.
So what if it's true? What value is added to the blog entry by making that statement? I don't see any, so then the question becomes, why make a statement like that in this context, regardless of it's truth?
The answer is that it's a dog whistle, meant to convey a specific message (RMS is too ideological, RMS is petty, RMS demands complete ideological submission, RMS is a control freak, etc.) to sympathizers, without yourself appearing to dirty yourself with making the attack explicitly. It might work but it makes you look all the more foolish not only for making gratuitous personal attacks, but for attempting to hide them.
"...campaign to rename Linux as GNU/Linux." funny stuff, to get Linux you can go to kernel.org, where do you go to get "GNU/Linux" ? (Free Software idiots)
Well, there's a difference in naming schemes here. We name the operating systems from MS for Windows. They run the ntoskrnl.exe kernel. There's no colloquial name for the windows kernel AFAIK.
The free operating systems however have richer naming schemes. Take for instance Ubuntu (quote from ubuntu.com):
"Ubuntu is a community developed, Linux-based operating system ..."
It is based on Linux, meaning Linux is the kernel.
The Linux kernel is what you get from kernel.org. In addition to the kernel you will need a range of tools, applications and so on to build an Operating System.
Those tools and applications often originate from the GNU project.
Which is why RMS urges us to use the denomination GNU/Linux when talking about OS's based upon Linux and GNU tools.
When we use only the name Linux for the whole operating system, it's because it is shorter and a widely known term. In the strictest sense it is erroneous.
Read more at http://en.wikipedia.org/wiki/GNU/Linux_naming_c...
And to answer your question: You go to anyplace on the internet that can supply you with a distro to get GNU/Linux.
GNU was a famous project back in the early 90's and so was Minix and so was Linux and so was BSD.
The GNU community was building their operating system (Hurd). Minix had one, but was not licensed for commercial use and the BSD folks were initially not set for running on low-end 386 machines.
Mind you, the GNU Hurd was built on top of the joint BSD + CMU Mach kernel. And you have never seen Richard Stallman refer to Hurd as a "BSD/CMU/GNU/Hurd system". Or call the Hurd a "CMU/Hurd" operating system or the "Mach/Hurd" operating system. He never thought about crediting others that were not part of his own movement (GNU).
Linux appeared in this environment, it was a toy operating system, and the community that was formed around Linux put together the operating system from the kernel, and anything they could get their hands on. They built a car out of scrap metal essentially.
They used GNU code, BSD code, public domain code, Usenet code, MIT code, CMU code, anything they could get their hands on.
This was a community that was born *out of the Linux kernel* and that happened to use scrap tools from anywhere they could. Just like RMS was building his Hurd out of anything he could (BSD/CMU code that he does not credit) the Linux community did not credit every possible source in the name of the project.
I am all for giving credit to RMS for his work, but I do not see myself calling Linux a GNU/BSD/CMU/X11/GNOME/KDE/Xfce/Blender/Apache/Linux system.
In the same way that I do not say Mozilla/Firefox, Mozilla/Thunderbird, Sun/MySQL, Apache/Hadoop, Guido/Python. I say Firefox, Thunderbird, MySQL, Hadoop, Python.
And there is a lot of story behind each name, but being a prick about "Mozilla/Thunderbird" is not going to matter a bit, other than confuse people.
what are "Usenet code" and "CMU code" ?
"I am all for giving credit to RMS for his work, but I do not see myself calling Linux a GNU/BSD/CMU/X11/GNOME/KDE/Xfce/Blender/Apache/Linux system."
I wonder why they start calling it Linux in the 1st place...
I loved that movie!
I don't like living that way, myself.
I've always thought that the "naming wars" were inane and self-serving: language has a life of its own, and trying to bully people into calling "Linux" "GNU/Linux" is as doomed to failure as l'Académie Française's attempts to insist that the French populace all call their Walkmans "balladeurs" and their emails "courriels"...