Slashdot Mirror


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).'"

43 of 443 comments (clear)

  1. Does anyone really use it? by Nursie · · Score: 4, Insightful

    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?

    1. Re:Does anyone really use it? by shutdown+-p+now · · Score: 3, Interesting

      wxWidgets is rather dated, though, and that's by design, making for rather awkward API. I mean, have a look at this:

      "wxWidgets does not use templates (except for some advanced features that are switched off by default) since it is a notoriously unportable feature."

      In 2009! Notoriously unportable, seriously? Basic template stuff (enough for generic containers, for example) has been perfectly portable since late 90s! But no, they don't want templates, which is why you get to write gems like:

      class Foo { ... };
       
      WX_DEFINE_ARRAY(Foo, FooArray);
       
      FooArray foos;

      I'll take Qt any day, thanks. It doesn't look any worse than wxWidgets in terms of "native" (even if it achieves that differently), but it's much more powerful, and the API is better. Now that both are LGPL'd, I really don't see any advantage wxWidgets might have.

    2. Re:Does anyone really use it? by shutdown+-p+now · · Score: 4, Informative

      That's the C++ API. Which is completely and utterly irrelevant if you are developing in Python rather than C++.

      wxPython API has its own flaws, which are just as huge. For example, event handling via message maps, which is directly ported from the C++ API (which in turn got it from the abomination that is MFC). I mean, seriously, this isn't idiomatic Python:

      ID_EXIT=110
      filemenu= wx.Menu()
      filemenu.Append(ID_EXIT,"Exit", "Terminate the program")
      wx.EVT_MENU(self, ID_EXIT, OnExit)

      A numeric "ID_EXIT" in a supposedly object-oriented framework - WTF?

      Meanwhile, in PyGTK, it's all just objects as it should be, with no manually defined numeric IDs:

      file = gtk.Menu()
      file_exit = gtk.MenuItem("Exit")
      file_exit.connect("activate", OnExit)
      file.append(file_exit)

      And PyQt is even better:

      file = QtGui.QMenu()
      file_exit = QtGui.QMenuItem("Exit")
      file_exit.triggered.connect(OnExit)
      file.addAction(file_exit)

    3. Re:Does anyone really use it? by Anonymous Coward · · Score: 3, Insightful

      If Qt used real C++ instead of its own language variant, it would probably be one of the top on my list. But until then, I just can't stomach it, even though part of me wants to use it.

      gtkmm can do it. wxWidgets can do it. Why does Qt need to pervert the language?

    4. Re:Does anyone really use it? by Sax+Maniac · · Score: 3, Informative

      Wha? Qt??!

      You mean the toolkit that requires a goofy cfront-style precompiler and comes with their own string class? Sure, it uses templates, but it's hardly a shining star of modern C++.

      --
      I can explanate how to administrate your network. You must configurate and segmentate it, so it can computate.
    5. Re:Does anyone really use it? by b4dc0d3r · · Score: 3, Funny

      C++ WxWidgets was a niche solution for a temporary problem. It's basically a portable copy of MFC with a few extra features.

      I got all excited about cross-platform GUI work, bought the book, got 3 chapters in, and all of a sudden had a huge WTF moment. Seriously, it was like looking at a painting of attractive women bathing, then you realize they are guys, and they are having sex and killing each other in the most creative ways imaginable. Wondering how I misinterpreted it at first, trying to see the original conception again, and feeling suddenly awkward about the erection is about as close of a metaphor as I can give to that moment.

      With scripting languages I'm sure it's all cool and stuff, but for C++ you'd be better off holding someone's grandmother for a Linux GUI ransom. Or, if you're really super crazy, try Qt instead.

  2. Why doesn't Miguel just go to work for Microsoft. by kurt555gs · · Score: 3, Insightful

    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 *
  3. Debugger by Spykk · · Score: 5, Funny

    It looks like MonoDevelop finally gets a debugger. That was really the last thing tying me to Visual Studio for .net development.

  4. Mono Blows (hint, where's FW 3.5) by tjstork · · Score: 4, Insightful

    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.
    1. Re:Mono Blows (hint, where's FW 3.5) by tjstork · · Score: 5, Insightful

      Wow. Imagine, an open source project cloning the functionality of a commercial product that doesn't support the latest features of the commercial product.

      Yes, but the commercial product is free as in beer, and the open source product is moving to be free as in beer only, so what's really the point, except to get locked into a clone of another technology?

      I mean, if you are that into .NET, why not just use Windows?

      --
      This is my sig.
    2. Re:Mono Blows (hint, where's FW 3.5) by steveha · · Score: 4, Informative

      Please provide a link to the FSF claiming that the LGPL is "less free" than the GPL.

      Are you trolling? They renamed LGPL from the "Library" GPL to the "Lesser" GPL, because they feel it is less free. It's baked right into the name that they feel it is less free.

      But you asked for a link. Here you go:

      Using the Lesser GPL for any particular library constitutes a retreat for free software. It means we partially abandon the attempt to defend the users' freedom, and some of the requirements to share what is built on top of GPL-covered software. In themselves, those are changes for the worse.

      http://www.gnu.org/licenses/gpl-faq.html#WhySomeGPLAndNotLGPL

      Just in case that wasn't clear enough for you, let me rephrase it: according to this gnu.org link, the LGPL does not protect users' freedom as well as the GPL. It does not maximize freedom as well as GPL. In short, it is less free, according to gnu.org.

      Remember that GNU and FSF are all about the users' freedom. Freedom of any developer to make proprietary software is not viewed as a good thing. A license like GPL that restricts the ability of developers to make proprietary software is viewed as more free.

      On the other hand, fans of the BSD license argue that it is "more free" because anyone may do anything with the software. GNU and FSF reject this idea.

      steveha

      --
      lf(1): it's like ls(1) but sorts filenames by extension, tersely
  5. good start! by Anonymous Coward · · Score: 5, Funny

    maybe next they'll remove all the non-GPL code as well.

  6. Is this the closing of Mono? by GreatBunzinni · · Score: 4, Interesting

    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.
    1. Re:Is this the closing of Mono? by AntiDragon · · Score: 3, Insightful

      Actually, this.

      LGPL is not "closed" - you still have to release the source code if you distribute software containing LGPL components. But what version of the LGPL are we taking about here? Since it's very easy to combine or cripple the LGPL'd parts so that they either rely on propritary or patent encumbered components in a way that can't be acheived with a full GPL product. Does the LGPL v3 protect against Tivoisation in the same manner intended by the GPL3? (Yes, I could go read the license but...it's long...and I'm tired..and others already have done so!).

      By the way, I'm not commenting about the suitability or preference of a particular licence - I'd just like to know what the implications are in this case.

      --
      "...So I hung back and lurked. For 18 months. Can't beat a good old-fashioned lurking."
  7. Re:Why doesn't Miguel just go to work for Microsof by morgan_greywolf · · Score: 3, Insightful

    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.

  8. Re:Why doesn't Miguel just go to work for Microsof by AlexBirch · · Score: 3, Informative

    To be fair, OpenOffice.org isn't GPL, yet that's the text editor / presentation software I use.
    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 .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.

  9. A Prelude to Charges... by tjstork · · Score: 3, Interesting

    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.
    1. Re:A Prelude to Charges... by codewarren · · Score: 5, Insightful

      That makes sense only if the next step in this plan is to make it work, add the features people want, and get people to actually use it.

  10. This makes sense by Norsefire · · Score: 4, Interesting

    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.

  11. Re:I think it's funny by Anonymous Coward · · Score: 5, Informative

    They are up to 3, and have a lot of 3.5 finished, but why let facts get in the way

  12. Sorry, Miguel by seebs · · Score: 5, Funny

    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/
  13. Re:Why doesn't Miguel just go to work for Microsof by backwardMechanic · · Score: 5, Funny

    OpenOffice.org is your TEXT EDITOR? Oh boy.

  14. Re:Now for business use by Lumpy · · Score: 4, Informative

    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.
  15. Re:I think it's funny by miguel · · Score: 4, Interesting

    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.

  16. Eternal game of catch-up by tepples · · Score: 4, Insightful

    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.

    1. Re:Eternal game of catch-up by miguel · · Score: 4, Informative

      As the other poster said, the fact that we do not have 1:1 parity has never been a problem.

      Some other technologies that are subsets and are wildly successful:

      * Android's Java is not a 1:1 mapping to Java either, and that has not prevented it from being successful.
      * iPhoneOS is not MacOS 1:1, and yet, it is incredibly successful.
      * Chrome the browser, does not have every feature of Firefox, that did not stop it either.
      * JBoss is a subset of the full J2EE stack, and for years it has been wildly successful.
      * Linux for years was not even POSIX compliant, and yet, many of us jumped on it, and it became wildly successful.

      In Mono we implement what makes sense, and what people are actually using in day to day applications, we do this using metrics that we obtain from our Mono Migration Analysis that helps us identify which APIs are used, by how many applications and we have collected this data from some 10,000 applications:

      http://go-mono.com/momareports/

      Call this the data-driven prioritization of development.

      Mono was born as a technology to bring the best that .NET had to offer to Linux, this was initially the c# language and the core libraries. As time went by, Mono evolved in two directions:

      (a) Organica growth: as the Mono community grew, we identify missing features, we envisioned better ways of doing something and created tools, APIs, languages and extensions that mattered to us. In this category you can find things like Gtk#, Taglib#, Cairo#, Cecil, Mono.Options, Mono.Security, Mono.Data, Mono.Math, Mono.Management, Mono's C# REPL, Mono's SIMD extensions, Mono's large array support. Mono's dynamic JIT extensions, Mono's static compiler and much more.

      For instance, today, more than 350 applications on the AppStore and 10 of the top 100 apps in there are built using Mono.

      (b) Better compatibility with .NET: this is a simpler process than coming up with our own APIs. The .NET APIs are documented, there are thousands of applications to test the implementation against, the community is fed directly from the largest middleware stack in the world, so it made sense for us to implement these pieces.

      Is it correct that we do not have a full implementation of .NET, there are a few reasons for this, now with numerals:

      (i) Some APIs are Windows specific, and makes no sense to bring to Linux, in particular things like System.Management which is a thin wrapper around WMI. Our advise: replace that code with Linux and MacOS specific code and use one or the other at runtime.

      (ii) Some APIs are too larger for us to take with our current community. This includes things like WPF and Workflow. If someone steps up, we will embrace them, but until that happens, we are focused on improving the other areas that have more users and that we have more requests to implement. Additionally, the WPF "lite" is a killer stack (also known as Silverlight).

      (iii) Focus, we do not want to spread ourselves too thin.

      As for .NET 4.0: we are not too far from having the core be 4.0 compliant, it is a nice upgrade to the solid 3.5 release. For instance, our C# compiler is already a full C# 4.0 compiler, and we already provide features that Microsoft wont offer until 5.0 (embeddable, reusable compiler, see C# REPL).

      Moonlight is behind Silverlight, but I am not driven by despair, I am driven by the world of possibility. If I were driven by despair, I would not have written a single line of code.

      If Silverlight never succeeds, then who cares how behind Moonlight is. But if Silverlight succeeds, and Linux users want to access that content, but the feature is either broken, not implemented or missing in Moonlight, those users will be in a position to contribute the code, and everyone wins.

  17. Removing the GPL code. by miguel · · Score: 5, Informative

    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.

  18. Re:Good. by ShadowRangerRIT · · Score: 5, Insightful

    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
  19. Re:"Free" is relative. by MightyMartian · · Score: 3, Insightful

    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.
  20. Re:Why doesn't Miguel just go to work for Microsof by selven · · Score: 4, Funny

    Yeah, that's a pretty decent text editor. I prefer MS Paint.

  21. Re:Why doesn't Miguel just go to work for Microsof by KiloByte · · Score: 5, Insightful

    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.
  22. Re:I know it's now LGPL but I couldn't resist ... by shutdown+-p+now · · Score: 4, Interesting

    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).

  23. Re:Why doesn't Miguel just go to work for Microsof by poetmatt · · Score: 4, Insightful

    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.

  24. Re:Why doesn't Miguel just go to work for Microsof by shutdown+-p+now · · Score: 3, Informative

    It's not a rumor.

  25. Re:Why doesn't Miguel just go to work for Microsof by gbjbaanb · · Score: 3, Informative

    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.

  26. Re:Good. by visualight · · Score: 4, Interesting

    .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.
  27. Re:Whining little babies. by dghcasp · · Score: 5, Informative

    The internet was basically built on the GPL, and most of the code that makes it go was built using the GPL

    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?

  28. Re:Why doesn't Miguel just go to work for Microsof by aztracker1 · · Score: 3, Insightful

    *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
  29. Re:Now for business use by Grishnakh · · Score: 4, Interesting

    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.

  30. Re:Why doesn't Miguel just go to work for Microsof by bcrowell · · Score: 4, Interesting

    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.

    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.

  31. Re:Why doesn't Miguel just go to work for Microsof by steveha · · Score: 3, Insightful

    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
  32. Re:Why doesn't Miguel just go to work for Microsof by Arker · · Score: 4, Insightful

    "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.
  33. Re:sigh by Abcd1234 · · Score: 3, Insightful

    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).