All GPLed Code Removed From MonoDevelop
rysiek writes "A few days ago, Miguel de Icaza wrote on his blog that the whole of MonoDevelop is now 'free' of GPL-licensed code. 'MonoDevelop code is now LGPLv2 and MIT X11 licensed. We have removed all of the GPL code, allowing addins to use Apache, MS-PL code as well as allowing proprietary add-ins to be used with MonoDevelop (like RemObject's Oxygene).'"
I know I'm an old fashioned luddite (I code with nedit, gcc and Makefiles), but does anyone use MonoDevelop?
MS does free (but not open) versions of its dev tools already, and frankly if you're using Mono you're probably an MS guy who wants his stuff to work on linux rather than a *nix dev anyway. Aren't you?
No GPL? Actually is Mono really that important any more? Most new software development is going to be on iPhone BSD, Android, and Maemo Linux. Needing legacy .net is nothing anyone cares about.
I think this shows Miguell's true pawn colors.
* Carthago Delenda Est *
It looks like MonoDevelop finally gets a debugger. That was really the last thing tying me to Visual Studio for .net development.
You know, if you are going to devote your life to making a C# clone on Linux, then at least quit screwing around with applications and focus on the language. I mean, come on, where's WPF? Where's WCF? Where's LINQ to SQL?
Mono, you suck.
This is my sig.
maybe next they'll remove all the non-GPL code as well.
Does this sign the closing of the Mono project? And can anyone tell me, since this fundamentalist stance against the GPL and the alleged impending patent sword hovering over the Mono users' heads, what exactly is there to attract people to adopt it as their developing platform?
Slashdot, fix your code or at least hire someone who is competent at it to do it for you.
So you're saying you think that most new software development will be for mobile-only OSes? Mobile apps may be okay for lots and lots of things, but I don't think that mobile apps will ever completely replace the traditional desktop applications. If anything, I see home-based computing moving in the direction of more and more LAN integration and more and better multimedia capability, with the hottest toys these days being media servers, wireless networking, faster broadband connectivity and more and more personal communications, including voice, video, IM, teleconferencing, etc.
The corporate network as it stands today will remain mostly the same, but with everything converging more towards service-oriented architectures, virtualization and cloud computing with dynamic, demand sensitive services and networks.
My blog
To be fair, OpenOffice.org isn't GPL, yet that's the text editor / presentation software I use. .NET. That said, I've never heard of anyone using it with Mono.
.NET and C# are pretty amazing technologies, especially with LINQ and Lambda expresssions, couple that with IronPython and you have a cool system.
Are you going to stop that as well?
You'd be surprised at how many corporations are going with Sharepoint, it's the silent Apache HTTPD killer and yes, it uses
By removing GPL code, the Mono team has laid the groundwork for a closed source, commercial implementation. You watch. Mono is going to become a product, something that will be an instant-cripple for any Linux distribution that comes to rely on it.
This is my sig.
The GPL is great for standalone applications but if you want to allow developers to make addons you really have to rethink it. Yes, it ensures that any addon made for the application will be free software however you have to consider the tradeoff; GPL it: everything is GLP'd, some companies/people won't develop or release addons; Other license: non-freesoftware addons may be developed, companies/people will have no reason now to release their software but it may not be open.
So it depends on what you value more; having the software but maybe not the freedom, or not having the software.
Obviously Stallman would rather the software was never created if it wasn't open, so the GPL wins for him there.
Personally I prefer the Artistic License 2.0; all the freedom and protection of the GPL without the virality.
They are up to 3, and have a lot of 3.5 finished, but why let facts get in the way
Bill's still happily married. I really don't think this is working.
My blog: http://www.seebs.net/log/ --- My iPhone/iPad app: http://www.seebs.net/seebsfrac/
OpenOffice.org is your TEXT EDITOR? Oh boy.
You mean the company you work for hates GPL. The last 5 I worked for, that includes fortune 100 companies like AT&T and Comcast, Loved the GPL and OSS. You should find companies that are nor run by undereducated management that is afraid of the GPL.
Do not look at laser with remaining good eye.
Various pieces from "olive" graduated into main Mono in the past year, including WCF, LINQ to Objects, LINQ to XML and WindowsBase (they are all in Mono 2.6)
The missing pieces (Workflow Foundation and Presentation Foundation) are not part of our plan.
By the time Mono finishes compatibility with .NET Framework 3.5, Microsoft will have finished Visual Studio 2010 and .NET Framework 4.0. Likewise, Moonlight is perpetually a version behind Silverlight, rendering it unable to view actual web sites that use Silverlight.
We removed the GPL code in MonoDevelop for a couple of reasons:
(a) to allow it to become a platform that third-party plugin and add-in developers can target.
(b) to allow us to consume open source code that would otherwise conflict with the GPL (MS-PL licensed code, Apache licensed code, and original BSD licensed code).
Notice that (a) is the norm for Eclipse and Visual Studio, and that the ecosystem of third party plugins relies on this, both Eclipse and Visual Studio would be severely limited if they limited the plugins to be all GPL licensed. As I explained on the blog post, there are current users that need to run their non-GPL code inside the IDE.
We want more third party developers to target MonoDevelop, and we want these third parties to consider MonoDevelop a platform that they can target without forcing a license on them. Similar to how the Linux operating system can run code licensed under any license.
The second reason is just a practical one. In the .NET open source ecosystem there are plenty of libraries and tools available under the MS-PL, Old and New BSD and Apache 2 licenses and we want to be in a position to use those libraries without rewriting it. We already do, and it has saved us a lot of time.
Right, because Microsoft is making a profit off licensing the .NET framework. Wait, you mean they don't charge a cent for it? And C# is a better language than Java, with the Mono project providing cross-platform compatibility, so Windows users have an easier time migrating to Linux if they so choose? Clearly I should listen to random /.er and forswear all use of anything that "supports" "Microsoft products" in any way, including the OpenOffice; after all, it lets people read and write Office documents, and by doing so, indirectly enables the Microsoft hegemony.
P.S. Yes, C# being better than Java is personal opinion. I've used both, Java for two years in school and one and a half years in the workforce, C# for a little under a year in school and half a year in the workforce (plus a few years of various other languages, mostly C/C++ and, yes, Perl). For developers, the lack of rigid ideological adherence to OO dogma is quite helpful; delegates for callbacks and "pass-by-reference" for arguments instead of inane wrapper classes for both (yes, pedantic types, I know it's all pass by reference, but you know what I mean), not needing to think about auto-boxing as much (since .NET collections of primitives really are primitives, not boxed primitives), operator overloading and structs to enable the creation of relatively efficient and easy to use numeric types, etc. I think both languages have merit, and I think both languages are improved by the competition (e.g. without C#, I'm not sure Java would ever have introduced generics, since it violated the spirit of OO). But I'm not going to reject C# just because MS made it.
$_ = "wftedskaebjgdpjgidbsmnjgcdwatb"; tr/a-z/oh, turtleneck Phrase Jar!/; print
Frankly I could care less. The Mono guys can do anything they like. I wouldn't touch Mono with a ten foot pole, for two reasons. First of all, I see no point to using it. Second of all, I wouldn't trust Microsoft with a nickel, let alone anything I was developing.
The world's burning. Moped Jesus spotted on I50. Details at 11.
Yeah, that's a pretty decent text editor. I prefer MS Paint.
Alas, Mono is still a part of the default Gnome distribution, just so they can have a note taking applet which takes 189MB memory (counting libraries used by it and no other process) and takes several seconds to start on beefy hardware while the C++ port of that very same code uses 5MB and starts near-instantly.
Even worse, there are folks pushing Banshee as the default music player so there's another dependency on Mono.
The sooner we get rid of Mono installed by default, the safer we'll be from this trap.
The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
Thus begins the Free-Free Software movement.
Begins? BSD guys have been trying to get rid of all GPL (including LGPL) in the base distro for a looong time - hence the planned migration to Clang (I believe GCC was the last remaining bit).
saying GPLV3 is too strict when we know the specific issue at hand here, means that it's just that proprietary things can still be embedded in GPLV2 and can't in GPLv3. So when "too strict" means "you can't shove proprietary shit into a free and open system", that tells me that MS and the lackeys are having quite a hard time dealing with open source.
It's not a rumor.
Yes, I am surprised at how many corporations are going with Sharepoint, yet its such a pile of w*** almost *everyone* at our corp thinks its pants (there are a few corporate yes-men lackeys who 'think' its good). Nobody can find anything on it, even adding search simply means we get thousands of hits for simple terms.
I can't understand why its spreading like an unfortunate rash at a sex party. Maybe the bosses will realise how bad it is and can it after it stops being used for a few months, but its always hanging in there, someone will post a document to it and suddenly its back to being a essential tool in everyday use.
.Net sucks on it's own, not because Microsoft made it. I think it's crap and I think Mono is just cross platform crap. My list of languages that suck: .Net|Mono
VisualBasic
Java
RubyonRails
All 'framework' languages that make it easy for people to crank out bloatware.
Last month I replaced 120MB of ruby dependencies with 14 bash scripts. But it seems like every time I turn around someone is presenting me with a new sack full of ax handles and asking me to alter our filesystem to support it. The current bane of my existence is an 'unsupported' gui .net app that won't run in anything except 1.49-somethingsomething.
My opinion is that how easy it is to implement your ideas is the _least_ important consideration, but so many programmers seem to think it's the only one that matters.
Samsung took back my unlocked bootloader because Google wants me to rent movies. They're both evil.
You mean built on things like TCP/IP (BSD 4-clause) and Unix (ATT License) that enabled communication between networks?
Or like sendmail (BSD Licensed) that facilitated adoption of user@example.com email addresses, instead of the dominant mixed!bang!and!right%associative!email addresses and the X.400 C=US;A=IBMX400;P=EMAIL;G=firstname;S=lastname;O=engineering;OU=email;OU=internet-connectivity style of addresses?
Or like Usenet (various parts under various BSD licenses) that facilitated the exchange of information, software, and porn before the web even existed? The one that Linus posted his early Linux sources to?
Or like FTP (BSD license, and/or ATT License) that allowed archiving and known-distribution-points of software way before google made it easy to find things?
Or like web browsers (all derived, more or less from NCSA Mosaic) which was never open-source, but required paying license fees?
Or like web servers, like Apache, which had (has) a license that isn't GPL compatable?
Can you even name any important GPL software (other than emacs) that is in wide use, is important, and is non-derivitive of something already existing under a BSD or proprietatry license?
gcc: derivitive. Every company around provided c compilers.
linux: derivitive. Ever hear of Unix?
*sigh* they moved to LGPL, which means you can distribute it with a better compatibility with other non-GPL plugins (those Apache, MPL, BSD or other licenses). If you modify the source, it still falls under GPL rules, it merely allows for bundled distribution with non-GPL code. It's all open-source and the main package is simply LGPL, or are you saying you don't use/reference any LGPL libraries in your code. Also, I'd presume that you don't use any Gnome or GTK libraries either.
Michael J. Ryan - tracker1.info
I really hate Slashdot moderation. This isn't a troll, it's a perfectly valid opinion and one that I agree with. What's with all the MS shills having mod points here anyway?
The last two companies I worked for (one being Intel) were also very large, and had no problems with the GPL and OSS. Intel releases tons of GPL code, and contributes tons of code to the Linux kernel (in GPL of course). Intel is smart enough to know how to use GPL code to their advantage, and not be stupidly afraid of it. My last company (I'll start saying who that was after they're at least 2 employers behind me) also did lots of Linux kernel development.
My current company isn't as smart, unfortunately. They're starting to develop a Linux-based product, but they're pretty paranoid about the GPL too, and are looking for ways to be able to use GPLed code without contributing anything back (nice, huh?). They don't seem to understand that contributing changes back means not having to maintain your own fork, which is a PITA.
Hmm...I tried to verify the statement about the 189 MB and failed, but maybe I'm just using the wrong method. I did a free -m, loaded tomboy, and then did another free -m. The result was only a 10 MB change in the amount of free memory.
It's true that tomboy is slow-loading on my (relatively fast) hardware. It's also true that it uses quite a bit of disk space. I did apt-get remove tomboy f-spot libmono* && apt-get autoremove && apt-get autoclean, and that freed up 64 Mb of disk space. If you're looking at, e.g., how much you can fit on a CD-based linux distro, 64 Mb is a heck of a lot to dedicate to something that's only needed for the sake of one applet.
Find free books.
Alas, Mono is still a part of the default Gnome distribution, just so they can have a note taking applet
Oh, "just" so they can have a single applet? It couldn't possibly be because they think it is a generally useful way to develop applications, such as F-Stop and Banshee?
Mono may or may not be a good idea, but you are framing your argument in an intellectually dishonest way here. That note-taking applet ("Tomboy") may be the only thing in standard GNOME that needs Mono right now, but I'm pretty sure that there will be others.
Even worse, there are folks pushing Banshee as the default music player so there's another dependency on Mono.
See? Then it won't just be Tomboy, there will be other things using Mono.
I haven't tried C#, but a lot of people seem to like it. If having C# means I get more free software to play with, I'm in favor of that.
The major argument I have seen against Mono is "Microsoft is just waiting and they will assert patent claims!!" In that case, the only thing that they can do is force people to stop using C# and Mono. In which case, all the Mono apps will be pulled or re-written. And at that point, you would have what you seem to want: no more Mono in GNOME.
That is the worst-case scenario. And I don't see it as being bad enough to try to keep people from using Mono. If people want to use Mono to write free software, that's fine with me.
I'm curious: now that Java is becoming fully free, would you support re-writing Tomboy and F-Stop and the others in Java? That way, instead of being bloated and slow C# applications, they could be bloated and slow Java applications. Would you be happier?
In my day job, I write wicked fast C code (small memory footprint, too). When I write software on my own for fun, it tends to be Python, which is even slower than C#. Do you have a problem with Python too?
steveha
lf(1): it's like ls(1) but sorts filenames by extension, tersely
"Only" 10 MB? How utterly absurd. And yes I get that in context to the claim made by the GP you have a point. (Possibly the GP has binaries compiled with debug symbols, or possibly *you* already have over a hundred megs of mono libraries loaded for something else and dont realise it.)
But just wow, only 10MB for a silly little virtual notepad. That's 256 times the entire system memory on my first PC. Which was a much more accessible and "user-friendly" machine than you can buy today, with a good DE built right in. It appears computer science in the intervening time has been exclusively focused on driving hardware purchases...
=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Friends don't let friends enable ecmascript.
Wake me up when you demonstrate it's not (I've issued this challenge many times, and no one's managed to achieve it).
Hint: Patents are published 18 months after filing, and a patent must be filed on an invention within a year of publication, otherwise the inventor forfeits the right to patent the invention. Furthermore, patents can only be submarined if the inventor forfeits the right to file the patent overseas, something I highly doubt MS is willing to do. As such, if parts of Mono were covered by patent, we'd almost certainly know about it by now (certainly there are enough anti-Mono trolls that *someone* should've been able to come up with such a patent by now).