Slashdot Mirror
Ximian to Change License for Mono
A Commentor writes: "According to news.com Ximian is changing the license to Mono from GPL to a variant of the XFree license. Apparently this is due to a partnership with Intel." Update: 01/28 15:03 GMT by T : There's a story at NewsForge as well, where RMS weighs in firsthand on the license choice.
Just as glibc and gtk are LGPL and not GPL, switching the license for the class libraries to a license that allows commercial software to be used with Mono is a good move.
.Net may fizzle or end up being a bridge for viruses from Windows, which will make the choice of license less important, as no one will be using it. If it does work out, it might mean that you can finally buy Linux software at CompUSA.
;)
I would have preferred the LGPL, but an X-style license is better than a lot of alternatives.
Of course,
I'm not sold on the whole clone-MS thing. On the one hand, it could lessen MSFT's grip on the market. On the other, MSFT will probably maintain incompatibilities with Mono, making Mono much less relevant. For instance, I doubt that they will ship a ".Net clean" version of Office that would run on Mono. Ditto for other cash-cow programs. However, I'll bet that Minesweeper.NET will be one of the first successes for Mono.
Napster-to-go says "Fill and refill your compatible MP3 player", which is a lie. It's not MP3. It's WMA with DRM.
is that Intel and HP are contributing to Mono.
I find it somewhat amazing that these two would risk the wrath of Bill. HP I can almost understand, since they're in the Unix business (for now anyway), but Intel would be in big trouble if MS dropped support for Itanic in favour of AMD's Hammer.
It is tempting, if the only tool you have is a hammer, to treat everything as if it were a nail. - Abraham Maslow
I'd rather see pragmatism than evangelism at this point. Some form of .NET style framework is going to become a standard in the next few years, and I'd rather it were an open source one than an MS one. 50 volunteers and 5 Ximian developers simply don't stand a chance against MS. If it takes a BSD-style license to get Intel and HP on board, then so be it. Evangelize later, once you've got the leverage and mindshare.
I know that you read /. from time to time, as I got an e-mail from you in response to a posting. Perhaps you can enlighten us here, because I'm really confused.
In discussing the LGPL vs GPL for libraries, you mention the idea that if the ability doesn't exist outside of the library (ie readline) you should GPL it. Then, if someone wants to use your library, they need to GPL it, and this advanced free software.
However, if you are reimplementing a standard (i.e. glibc) then you should use the LGPL so that others can build on your work.
So, assuming we shared your goals of using licensing to advance free software, I still don't see how this hurts.
Right now, in the pragmatic marketplace, the Unix vendors are retreating up the ladder. Linux and GNU based systems are replacing the low-end UNIX system. Proprietary UNIX is slowly being confined to areas where Free Unix-like OSes can't perform. I think that worrying about liberating Unix users is quite silly. At this point, any markets that Unix competes in will belong to GNU when it matures to that level. UNIX isn't the enemy, its the advanced team. Crippling the commercial UNIXes in a Unix vs. MS fight really hurts free software, as we have a Free Unix, but not a free Windows. The Free Unix will displace the non-Free Unixes, but if the service runs on Windows, you won't liberate those users.
From this view point, I fail to see how this licensing change hurts thing? These classes are duplicates of the Microsoft classes. As they are based upon compatibility, you can't really do much with them directly. I don't see the leverage that even GPL'd versions give you.
If your goal is to prevent Sun from using this work to sell Solaris in this market, I think you are missing the situation here. The first choice that is made is Unix vs. WinNT. If WinNT wins, then your free tools are ignored. If Unix wins, then GNU systems get the job if they can handle it, otherwise a Unix is chosen. When the server is replaced in 2-3 years, it will likely be replaced by a GNU system.
We can't offer things that Sun and HP can. If they do the job, GNU systems kick in when they can handle it. If Win32 gets the job, you are unlikely to liberate them.
Please, explain how crippling the development efforts advanced free software?
GNUstep could have done wonders had the project been nearly completed 3-4 years ago. It is just coming to maturity now, and will likely me 2 years from true usefulness.
This industry moves quickly, and GNU is making it move faster. Any space gets eaten by Free Software within 5 years of existance now, with good prototypes in 2-3 years. Isn't it simply enough to speed up the Free Software Goliath? Why attack the Unix vendors, they're adopting the GNU way slowly as they can.
Alex