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

77 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 ceoyoyo · · Score: 2, Insightful

      I think it would be more likely you're a Linux/Mac developer who for some reason needs to write something for Windows. If you were a Windows developer you'd probably just use MS's tools and test with Mono.

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

    3. Re:Does anyone really use it? by VoidEngineer · · Score: 2, Insightful

      Exactly. It's particularly useful for those of us who want to port our .Net code library away from Microsoft tools. Having worked in an MS environment for many years, I have tens of thousands of lines of code in various utilities and research projects that I've written in .Net. A few years back, I made the switch to Mac/Linux, and would like to never touch a Windows machine again, if possible. But I still want my code library available. So, this tool works perfectly for my needs. I made a wise decision many years ago to limit my develop to .Net 2.0 libraries only. Because I've exercised self-control in my coding practices, my .Net 2.0 code is now pretty much cross-platform, now that Mono has pretty much implemented the entire 2.0 specifications. And with MonoDevelop, I now have a mostly full featured-replacements for Visual Studio (I'm really only concerned with line numbering, code formatting, intellisense, refactoring, and nUnit testing in my IDE). So, as far as I'm concerned, and I can do cross-platform Mono development on Linux/Mac from here on out.

      Of course, if you're trying to write .Net 3.5 or 4.0 code, there will be features not implemented yet, and it will be a pain. But it's great for 2.0 development.

    4. Re:Does anyone really use it? by gbjbaanb · · Score: 2, Interesting

      Yuo may jest about Javascript, but I really think its the future. Everyone wants easily-deployable, thin-client apps (well, everyone, I mean line-of-business people) that perform as well as thick-client apps. Now we're just about, almost, getting there with HTML5, WebGL and the like, and so a good javascript implementation could provide a nice GUI to a back-end processing cloud. .NET and similar will become obsolete if the above could be shown to be workable in practical terms.

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

    6. 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?

    7. Re:Does anyone really use it? by GreatBunzinni · · Score: 2, Insightful

      I second the idea that Qt kicks ass. Nonetheless, the design decision behind Qt's policy of forcing the programmers to drop the STL in favour of Qt's components such as container classes and string... Well, it sucks. It imposes on the programmer a non-standard way of doing things, it is a royal pain in the ass to integrate 3rd party components that rely on the STL and it plainly sucks to be forced to use a less mature API.

      --
      Slashdot, fix your code or at least hire someone who is competent at it to do it for you.
    8. 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.
    9. 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.

    10. Re:Does anyone really use it? by GreatBunzinni · · Score: 2, Insightful

      It appears you have a very odd definition of what "not forcing" means. Qt doesn't offer support in all of Qt's classes for STL containers and/or the standard C++ string objects. You cannot write a Qt app without being forced to use Qt's QString and/or Qt's containers. The only way you may use C++'s standard components is if you bring additional bloat and complexity to the application by converting Qt's data types and containers back and forth with STL's, which quite plainly sucks in multiple ways.

      But then again, if you had any experience writing apps with Qt and if you had the displeasure of having to incorporate a third party C++ component which relies on the STL you would realize that Qt does in fact forces the programmers to use Qt's containers and data structure. On the other hand, if you never had to deal with this problem then you would have no problem attempting to label that fact as bullshit.

      --
      Slashdot, fix your code or at least hire someone who is competent at it to do it for you.
  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. Good. by couchslug · · Score: 2, Insightful

    People who want to work for/shill for/suck up to Microsoft directly or indirectly should do that.

    Those who don't support that sort of thing should work to cut them off at the knees by not using their software and discouraging others from doing so.

    --
    "This post is an artistic work of fiction and falsehood. Only a fool would take anything posted here as fact."
    1. 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
    2. 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.
    3. Re:Good. by nurb432 · · Score: 2, Insightful

      Right, because Microsoft is making a profit off licensing the .NET framework..

      No, but they are smart enough to know if you can lock in as many people into your frameworks ( even if its just a virtual lock due to knowledge ), it only increases market share way down the road.

      You have to think of the BIG picture, not what you can see if you look around your cube walls.

      --
      ---- Booth was a patriot ----
    4. Re:Good. by aztracker1 · · Score: 2, Insightful

      I've seen crappy code in every language I've worked in... I've also seen elegant code in almost every language I've worked in... That's a pretty poor benchmark of a language. If that's your benchmark, then Python is simultaneously the best and worst language out there. Doesn't mean that I like it.

      --
      Michael J. Ryan - tracker1.info
    5. Re:Good. by msgyrd · · Score: 2, Insightful

      A cancer treatment from Microsoft would mean that you'd have to continually buy a license to maintain use of the treatment from them or they'd cut you off and let you die. You may survive, but you're enslaved to them. Then again, that's not far off from current medical practices either.

    6. Re:Good. by NotBorg · · Score: 2, Insightful

      How does software running on BOTH Windows and Linux create a lock-in?

      Seems to me that the lock-in is a world without Mono. Then if you .NET you are locked in to a Windows only world. They are going to .NET regardless of Mono's existence. At least with Mono users aren't locked into Windows only.

      Would you rather have something like where Flash comes from? A binary that runs on both but is closed up tight? Would you rather have Microsoft implement a closed .NET runtime blob that runs on Linux instead of an open source Mono?

      I don't see Mono as any more evil than Wine, Cygwin, Samba, FreeDOS, or the plethora of open source programs that run on both Windows and Linux. The logical extension of "hate Mono because it provides compatibility with a Microsoft frame work" is to hate all software compatible with any Microsoft framework. You should hate Firefox, Open Office, Apache, QT, and on and on. If it runs on a MS platform it must be supporting the lock-in right?

      The big picture is that Linux only is no better than Microsoft only. Interoperability between the two platforms helps both sides.

      --
      I want this account deleted.
  5. 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
    3. Re:Mono Blows (hint, where's FW 3.5) by TibbonZero · · Score: 2, Interesting

      We developed our initial product (imVOX... http://imvox.com/ in .NET for Windows, but then we wanted to move over to OS X and Linux as well. Instead of rewriting completely in Java or C (which we didn't have the time or money for on our schedule), we thought to use Mono. Otherwise creating 3 separate code bases to maintain and debug with a small team, Mono seemed to do the trick (for now). By no means do we claim that .NET/Mono or C# is the best thing in the world- but similar to using Rails, we needed rapid application development to get a shippable product out the door in order to raise more money. We didn't have time to write it in C on 3 platforms from the first day. I think this makes sense. When someone loads us up with cash- we'll probably re-write in C++ or something, but not today.

      --
      Tibbon
      tibbon.com
    4. Re:Mono Blows (hint, where's FW 3.5) by onefriedrice · · Score: 2, Insightful

      fans of the BSD license argue that it is "more free" because anyone may do anything with the software

      Including... making it non-free again...

      Oops.

      Yeah, oops indeed. Like so many before you, you have bought into the false belief that BSD licensed code can magically become non-free in some fashion that GPL code cannot. Let's go over this again. The only one that can relicense code is the copyright holder. Even then, that will not nullify the license of code which has already been licensed and released. This is all true whether the code is BSD licensed or licensed under the GPL. You cannot take BSD, and make it non-free, as you assert. The only rights you have are what the license itself grants you. In the case of BSD code, you can use it in combination with proprietary code and even decide for yourself how to license your changes (this in contrast with the GPL), but it is impossible for a user to just take the code and say "hence forth, this is now proprietary code; thus, nobody shall use it except I."

      If you still don't understand, I don't know what more I can do to help you.

      --
      This author takes full ownership and responsibility for the unpopular opinions outlined above.
  6. good start! by Anonymous Coward · · Score: 5, Funny

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

  7. Now for business use by Anonymous Coward · · Score: 2, Interesting

    Businesses really don't like the GPL. I'm not allowed to use any GPL stuff anywhere unless it absolutely, positively will never leave the intranet. However, many businesses love the LGPL. It doesn't restrict them. So, it still stays open source, and businesses will create plugins. I write open source software on my own time, so I appreciate open source, but if I was a manager, I wouldn't touch any of the GPLv2/3 programs/code ever.

    1. Re:Now for business use by Nursie · · Score: 2, Informative

      There's a huge difference between GPL tools (which we at HUGE_CORP I work for use lots of) and GPL code/components.

      We use binaries only, source could potentially lead to allegations of copying. And we make sure not to use any GPL code or components in our products so that we don't need to open them.

      But all-out avoid GPL? No way. We use linux as a dev platform (amongst others) and we use all sorts of FOSS tools with a huge variety of licenses in addition to some commercial stuff.

      You'd be a fool to make avoiding the GPL some sort of mandate.

    2. 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.
    3. Re:Now for business use by betterunixthanunix · · Score: 2, Insightful

      If using GPL software is so dangerous for business, why are so many companies running Linux in production environments? These are some of the most successful companies in the world, and they have been using Linux for a while -- where are the problems that you seem so sure would ensue from such a situation? If you remain close minded about the GPL, you will be missing out on a lot of high quality software...

      --
      Palm trees and 8
    4. 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.

  8. 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."
  9. 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.

  10. I think it's funny by gregarican · · Score: 2, Insightful

    Reading all of these comments and then seeing them modded as Troll or as Flamebait. When actually the comments are pretty much correct. Who really uses Mono? After all, isn't it loosely based on .NET version 1.1 still? What's the point?

    For Windows-based development you can fire up Visual Studio 2005 or 2008 Express edition without paying a dime and those are based on .NET 2.0 or 3.x, correct?

    Unless Mono has upped the ante and has actually moved beyond 2003-era frameworks I don't see its relevance...

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

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

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

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

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

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

    OpenOffice.org is your TEXT EDITOR? Oh boy.

  16. sigh by StripedCow · · Score: 2, Insightful

    wake me up when mono is ms-patent-free

    --
    If Pandora's box is destined to be opened, *I* want to be the one to open it.
    1. 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).

  17. Re:Use java instead by Pecisk · · Score: 2, Informative

    LGPL *is* free software.

    --
    user@ubuntubox:~$ stfu This server is going down for shutdown NOW!
  18. 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.

    2. Re:Eternal game of catch-up by christurkel · · Score: 2, Insightful

      Those three web sites that require Silverlight must be very important to you.

      --

      CDE open sourced! https://sourceforge.net/projects/cdesktopenv/
  19. Re:Why doesn't Miguel just go to work for Microsof by Again · · Score: 2, Funny

    OpenOffice.org is your TEXT EDITOR? Oh boy.

    Well at least he can do his own custom syntax highlighting without messing around in the "Preferences".

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

    1. Re:Removing the GPL code. by MasterOfMagic · · Score: 2, Informative

      Actually, they're just using the LGPL. If that bothers you, declare your copy to be GPL and follow the restrictions of the GPL, according to the LGPL:

      3. You may opt to apply the terms of the ordinary GNU General Public
      License instead of this License to a given copy of the Library. To do
      this, you must alter all the notices that refer to this License, so
      that they refer to the ordinary GNU General Public License, version 2,
      instead of to this License. (If a newer version than version 2 of the
      ordinary GNU General Public License has appeared, then you can specify
      that version instead if you wish.) Do not make any other change in
      these notices.

          Once this change is made in a given copy, it is irreversible for
      that copy, so the ordinary GNU General Public License applies to all
      subsequent copies and derivative works made from that copy.

          This option is useful when you wish to copy part of the code of
      the Library into a program that is not a library.

    2. Re:Removing the GPL code. by FreelanceWizard · · Score: 2, Insightful

      Linus is not a lawyer, and his statements should not be taken as legal advice.

      Licensing is entirely a legal issue, not a technical one, and the whole "when does linking and in what manner cause a module to be considered a derived work" question is an unsettled legal one (i.e., it has not been tested in court with regards to the GPL). nVidia's binary driver issue hasn't yet been tested because no one who has standing has been interested in suing over it. A lack of legal action doesn't necessarily mean that no legal action is possible. At any rate, Stallman and others seem to fall on the side that any kernel module is a derived work, which is why there's Linux-libre.

      "Trivially refuted," indeed.

      --
      The Freelance Wizard
    3. Re:Removing the GPL code. by KyleJ61782 · · Score: 2, Insightful

      There is no way that a court would require a plugin that merely uses a published interface to be released as open source. Consider the following situation:

      1) A GPLed project releases documentation describing functions that must be exported from a shared library in order for it to be a plugin.
      2) Some other author decides to write a closed-source shared library that exports said functions.
      3) In order to use the shared library, the GPLed product must initiate a shared library load and map the closed-source library into its address space.

      Nowhere in the above situation does the closed-source project link to the GPLed code, except when the GPLed code specifically initiates the interaction. Just because GPLed code interacts with closed-source code doesn't mean that the closed-source code must be open sourced--especially when the dynamic linking is performed by the GPLed code.

      Furthermore, consider a situation where there is a generic plugin interface that works for two different software packages: one closed-source and the other a GPLed. If a court says in the above situation that the plugin must be GPLed, what happens in this one? Does the logic extend to this situation?

      In my mind, it ultimately depends upon who is initiating the linking. If a developer links with GPLed code (dynamically or statically), the code that developer writes must be open sourced. But any code that a GPLed project links to cannot force code that it links to to become open sourced, otherwise entire software packages could be forced to become open sourced when they did nothing except write some software that a GPL software developer wanted to use.

      --

      I refuse to have a battle of wits with an unarmed person.
  21. 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.
  22. 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.

  23. Re:Why doesn't Miguel just go to work for Microsof by srh2o · · Score: 2, Informative

    I keep hearing these kind of arguments but reality shows us that contrary to these claims that use of GPL code is growing. The fact is that companies are used to licensing code and complying with the GPL is trivial compared with many of the other licensing steps that the average company has to comply with.

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

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

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

    It's not a rumor.

  28. Re:Why doesn't Miguel just go to work for Microsof by jonbryce · · Score: 2, Informative

    Sharepoint is an application that runs on IIS. IIS is what is replacing Apache here. Sharepoint replaces some of the content management systems you might run on Apache, whatever they might be.

  29. Re:Why doesn't Miguel just go to work for Microsof by ircmaxell · · Score: 2, Insightful

    I don't buy that. One of the biggest gripes that I have with the GPL (and I have released a fair amount of code under it) is that it promotes compliance through ignorance. Let me explain:

    So long as whatever you do is released GPL, you're fine (well, under 99% of the cases anyway). If you want to release under any other license, determining if it's allowable is a nightmare. Try to interface a non-gpl plugin with an application. There's no "easy" answer as to if you can do that. Every lawyer will say something different. There's no legal precedent with regards to how non-gpl code can interact with gpl code. So the "easy" way to comply is to just license your code GPL... Sure, there are black and white compliance cases, but the vast majority that I've looked at are well in the gray area. Can you dynamically link a non-GPL lib into a GPL program? Can you dynamically link a GPL lib into a non-GPL program? What about statically? More importantly, WHY? Now, explain that to a judge who has no technical background.

    Again, I'm not arguing with the ideals of the GPL, I'm arguing the ambiguity when it comes to interfacing with non-GPL code (At least from discussions and conversations I've had with lawyers and other prominent developers)...

    --
    If a man isn't willing to take some risk for his opinions, either his opinions are no good or he's no good
  30. 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.

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

    How do you know he isn't working for them already? Maybe this event is just the first step towards using the Microsoft license. It would make sense, because I'm sure Microsoft would like to get a working version of .NET to compete with everyone else.

    --
    Who would win this election: Andrew Weiner vs Andrew Weiner's weiner.
  32. Re:Why doesn't Miguel just go to work for Microsof by xtracto · · Score: 2, Funny

    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.

    So, at last Novel achieved the real objective of .NET? - to be a complete replacement of the Java technology! - even Microsoft could not do that! bah!

    --
    Ubuntu is an African word meaning 'I can't configure Debian'
  33. Re:Whining little babies. by stickystyle · · Score: 2, Insightful

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

    eh?

    • Apache; Apache license
    • BIND; BSD license
    • ISC dhcpd; ISC license
    • sendmail; sendmail open source license
    • TCP/IP; not sure, but definitly not GPL
    --
    Pluralitas non est ponenda sine neccesitate
  34. 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?

  35. 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
  36. Re:Whining little babies. by grotgrot · · Score: 2, Interesting

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

    Exactly which planet are you referring to, because it isn't this one. GPL v1 is from 1989. Depending on exactly what you want to count as "The Internet" you can put the start date as early as 1969 or as late as 1983. Commercialization and ISPs arrived in 1988 in the US. Cisco provided many of the routers used (started 1984). BSD was the main OS used for TCP/IP development and research. BBN had the "reference implementation". Every single one of these things predates the GPL. The BSD TCP/IP stack was ported to many other platforms, including Windows. One thing is categorically certain - the Internet was not built on the GPL. If anything it was built on BSD licensed software.

    For one thing, making you pay for all of our code you are secretly using for free.

    The GPL is not and has never been about price. It is about freedom to share, modify and use. You can charge whatever you want. You can even charge people a small reasonable fee to get the source code. It also depends on copyright law. Someone "secretly using" anyone's code without permission is violating copyright.

    I for one have had enough of the whining about the GPL and how restrictive it is.

    The GPL is restrictive because you cannot change the terms under which the code can be redistributed. It also applies to the whole program. For example if you add one line of GPL code to a 20 million line program then the whole program has to become GPL compatible. Note I use the GPL for most of my stuff and consider that the cost if you want to use my code. But it certainly is more restrictive. There is the LGPL which mitigates this but its use is discouraged.

    It seems to me, its only restrictions is you can't rip people off.

    "Ripping people off" is usually a financial thing. Google have built a multi-billion dollar empire using lots of other people's GPL code (eg Linux kernel) and have not paid them. The GPL allows you to use GPL code within a company and providing you do not distribute outside of the company you can use code as you see fit, so the original author gets "ripped off".

    Your view of the GPL is just plain wrong. It is about freedom and the restrictions are largely that you have to provide the same freedoms on the code you receive to others if you pass the code or derivatives on to others.

  37. Re:False dichotomy by thetoadwarrior · · Score: 2, Interesting

    Unless we start getting governments to enforce some sort of standard which means customers can return software or sue companies for releasing shit then the best thing for software is for it to be open so anyone can see it and fix it.

    Part of me thinks that computer languages are languages like no other and one should be able to see it and use other people's work, at the very least for inspiration. Like you can do with any other language.

    Another part of me thinks that true freedom means having the choice to close your code if you want because seeing the code isn't required to use your product.

    But again too often companies can effectively release beta shit and be paid hundreds per licence to use it. So what we really need, imo, is standards that stop that. You can argue that, unlike a car, you can't die from bad code but your life can effectively be ruined when your privacy is compromised.

    So how about striving for openness and higher standards in quality? If we get at least one of those we should be fine.

    The exception should be data. Your data should *never* be stored in a format that only one or two programs can read. It's your data and if the company goes under or just moves on to another product, you're fucked. That shouldn't be allowed.

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

  39. Re:Why doesn't Miguel just go to work for Microsof by Radhruin · · Score: 2, Informative

    Actually, Mono is completely different from Wine, and not even Wine is an emulator. It's a native implementation of the CLR and other .NET tools that run on Linux/BSD/etc. If you want to compare it to something, compare it to the JDK.

  40. Re:It is so sad... by onefriedrice · · Score: 2, Insightful

    It's sad that the headline here is about removing GPL code. Got a grudge against it?

    Why is it sad? The code isn't closing, it's just now licensed under different (arguably freer) licenses. Unless you're RMS or one of his disciples who believes that all code must be GPL or it's not truly free, I don't see why this should make anyone sad. Free code is free code, and contrary to somewhat popular belief, the GPL does not make free code more free than it is.

    Secondly, there are several reasons why a project might want to migrate away from GPL code, and none of those reasons have to have anything to do with having a grudge against the GPL. From a practical standpoint, avoiding the GPL also avoids many headaches related to source code and license mixing; this is especially important for a product which implements plug-ins since the legality of plugging some differently-licensed extensions into a GPL product is still uncertain. The GPL itself causes incompatibilities with certain licenses, so an easy way to avoid those types of problems is to avoid the GPL entirely.

    --
    This author takes full ownership and responsibility for the unpopular opinions outlined above.
  41. 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
  42. Re:Whining little babies. by Alcemenes · · Score: 2, Insightful

    I would expect the pedantic police will be out in force to correct your usage of the word "derivitive" but otherwise your point is well made. Personnally, I don't think the problem with the GPL is the license itself. I use it occassionally even though I prefer the less complicated BSD-style licenses. My problem are the legions of Stalmanistas who attack anyone who criticizes the GPL. These same people like to point out how using software licensed any other way makes you a slave to the developer yet they drive cars made by someone else, wear clothes produced by someone else, and often eat food that is prepared by someone else. Using their arguments they are just as much of a slave to the manufacturing and service industries as computer users are to software companies. The fact of the matter is, we are all a "slave" to something. We all enjoy having our choice but some seem to forget one very important choice; if you don't like something, then don't use it. You have that choice too. And please don't argue with me because I didn't make the same choice as you. I realize that is part of human nature, but there are bigger and more important things in life.

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