Slashdot Mirror


Mono Squeezed Into Debian Default Installation

pallmall1 writes "OS News reports that Debian developer Josselin Mouette got Tomboy accepted as a dependency for gnome in the next release of Debian (codenamed Squeeze). While that may seem like nothing big (except for the 50 MByte size of the Tomboy package), Tomboy requires Mono — meaning that Mono will now be installed by default. Apparently, Debian doesn't have the same concerns over using specifications patented by Microsoft and licensed under undisclosed terms that Red Hat does. Perhaps Debian doesn't believe that Microsoft might do something like Rambus did."

11 of 503 comments (clear)

  1. Call Upon the ECMA Code of Conduct by eldavojohn · · Score: 5, Insightful

    Perhaps Debian doesn't believe that Microsoft might do something like Rambus did.

    Rambus was chastised for their actions (like the linked article states). And I propose Debian approach this the same way someone would approach the Rambus situation from the beginning had they an inkling of Rambus' true intent.

    Even though Microsoft submitted the CLI and C# main components of .NET, MIcrosoft does hold at least one patent on the .NET infrastructure. So far, Microsoft has agred to offer these under a "reasonable and non-discriminatory (RAND) terms of use" and they are currently royalty free. No one seems to be clear on how you get this into writing but it's allegedly the way things are.

    Were I a Debian leader, I would simply approach Microsoft with the Mono code and the ECMA code of conduct and demand it in writing that for this snapshot of the code you have a forever royalty free to interact with .NET. Should they fail to comply with this request in a timely manner, I would submit all communications with Microsoft to ECMA in a motion to dismiss the aforementioned "standards" and remove Mono--and unfortunately Tomboy--from the Debian default package. I'd beef up the Debian wiki with details on how to get these two packages to fix this bug and focus on the bug for a near future release after Squeeze.

    At that point, sit back and let ECMA and the community at large hash it out with Microsoft. Better now than later when other things may depend on this package and Microsoft has you right where Rambus has every memory maker on the planet.

    --
    My work here is dung.
    1. Re:Call Upon the ECMA Code of Conduct by Aphoxema · · Score: 5, Insightful

      Microsoft may just have .NET patents and contracts for their own sake, as SOP. Pragmatically, it would be a mistake for them to sue Debian or Miguel. I think they realize that because they haven't yet gone after Miguel.

      Or they've already gotten him.

      --
      "Most people, I think, don't even know what a rootkit is, so why should they care about it?"
    2. Re:Call Upon the ECMA Code of Conduct by Hurricane78 · · Score: 4, Insightful

      Sounds to me like the "no bugs have popped up yet, so there are no bugs in the program" logic fallacy.

      If one company of all has proven to follow the rule, that if they have some strange clause in the contract, and on asking about it, they say that it's just for safety and will never be used in reality, they intend to use it as early and as often as possible, then it's with no doubt Microsoft. (Health insurance companies would come to mind too.)

      I think, given the happenings of the past, it is far more likely, that as soon as Mono became an essential part of Gnome, so that to remove it, you would have to kill Gnome entierly, Microsoft will load its weapons. ;)

      Which means that soon, the argument of both troll teams (the pro-mono and the contra-mono side act very trollish, I must say), will be settley, and we can go back to VI vs Emacs. ;)

      On another note: What's the point of Gnome again, now that Qt/KDE is open sourced? (Remember how Gnome started because it was not.) ;)
      Oh well, I am always for more freedom (and more choice, if it helps freedom), so why not? :)

      --
      Any sufficiently advanced intelligence is indistinguishable from stupidity.
  2. Incredible horrifying bloat by k-zed · · Score: 4, Insightful

    tomboy package "Description: desktop note taking program using Wiki style links"

    "..except for the 50 MByte size of the Tomboy package..."

    What's wrong with this picture?

    --
    we discovered a new way to think.
    1. Re:Incredible horrifying bloat by suffix+tree+monkey · · Score: 5, Insightful

      Indeed, that is my problem with Mono (or C#, for that matter) as well. We can't expect small, lean applications written in C# because of the language's design. C# is only good for writing code blazingly fast. Which is kind of silly to me, because as a semi-experienced programmer, I know that writing code is the easier part of software development.

      So yeah, the more Mono/C# apps we get into Debian, the slower and memory-hungry (and disk-hungry, but I find that a non-issue in general) it gets. However, most people with enough RAM just 'meh' it out, after all, there is no such thing as Page's Law, right?

      But it's not just Microsoft's products that bloat Debian. My personal windmills are applications like HAL, D-BUS, any gnome-*-daemon, any {Policy,Device,Console}Kit and so on. By the way, a useful hint - when a developer can't think of an original name and prefers to rip-off a name trendy at that time, expect the code to be as well thought-out as Nuka Cola Cherry.

      (I get agitated when software bloat is discussed, I know.)

    2. Re:Incredible horrifying bloat by TheRealMindChild · · Score: 4, Insightful

      "bloat" - I do not think that word means what you think it means.

      .NET is an ENTIRE platform. You likely could have a whole system where this is the only accessible API. Just like Java. Would you fault, say uTorrent, for having 40 megs of win32 dependencies?

      This is the unfortunate case of a .NET application being apparently the only one in the core system, so it gets all of the weight of the dependency on Mono. However, when a few thousand applications in the system are .NET, that kind of a dependency is not even a second thought.

      --

      "When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
  3. Re:What the F... by sydneyfong · · Score: 5, Insightful

    PS: From TFA (I confess not having read it in full before typing the above rant ... I did read TFA.... just not in detail ;-p)

    The news got out via a blog post by Debian maintainer Robert Millan, who maintains the Gnote package for Debian - Gnote is a non-Mono replacement for Tomboy written in C++.

    In other words, it's a non-story about two maintainers trying to get their packages accepted into the "default" installation (from TFA it sounds like it's an issue of what to include in the first CD). Yeah, raise patent concerns, size concerns, blah blah blah blah, but it all boils down to ego stroking and comparing dick sizes.

    Duh.

    --
    Don't quote me on this.
  4. Re:Yessss by Anonymous Coward · · Score: 5, Insightful

    As a .NET developer (at work), and a Linux user (at home), I don't like this idea. I'm sure you are going to label me "a big rabid stallmanist troll" for pointing this out, but those patents are real, at least if you ask Microsoft. And so is the agreement that gives Novell permission to distribute Mono.

    Now, why would Novell sign such an agreement? Easy: Because their legal department advised them to do so. From this we can conclude that Novells legal department has knowledge of legal risks concerning Mono.

    Microsoft has already shown that their patents are not for self defence only, when they sued Tomtom over several patents related to the FAT filesystem. Not only is FAT old, there is also nothing about FAT, that isn't obvious to someone writing filesystem. In other words: FAT is not even patent worthy. The .NET framework, however, represents a great value for Microsoft (for one thing, it's the first Windows API that doesn't suck big time), and it's got to have several patent worthy ideas in it.

    So, why would Microsoft want to protect something worthless like FAT, but not real value like the .NET framework?

    As I see it, it's not a question about if they are going to sue someone over the .NET patents. It's a question of WHEN and WHOM.

  5. Re:An interesting read on the subject by Jesus_666 · · Score: 4, Insightful

    The problem is that Microsoft has an extremely bad reputation. We expect them to do absolutely everything they think could be to their advantage because, well, that's how they behaved in the past - even going as far as subverting ISO to get their document format declared a standard.

    As long as Microsoft retains any control over .NET I won't feel safe around the platform simply because they could decide to screw over everyone at any time and given their past behavior I expect them to.

    Whatever Microsoft comes up with, it's either a fully integrated part of their software stack or too hot to get involved with. I don't want to get caught in the fallout of a patent lawsuit. That sounds paranoid but, well, Microsoft's actions so far have been fairly consistent.

    --
    USE HOT GRITS WITH STATUE OF NATALIE PORTMAN (NAKED AND PETRIFIED)
  6. Re:What the F... by Fallingcow · · Score: 4, Insightful

    Of course, it's under GPL so Gnote is within it's rights, but there's a thing called professional courtesy and respecting a developer's wishes.

    If it runs faster and takes up less space*, who cares what the Tomboy developers think? May the better app win, I say.

    *disclaimer: I have no proof that either of these are true, but it seems likely. If not, then Tomboy ought to thrive and Gnote will probably not gain many users anyway.

  7. FUD by gd2shoe · · Score: 5, Insightful

    This particular outburst of concern is FUD. Debian already has Mono in the "main" repository (as opposed to "contrib" or "non-free"). That alone is a statement that they are not worried about the "free-ness" of the package. Even if it will now be installed by default, it was already made available by default to every Debian installation. The difference is very superficial.

    If MS was going to go after them, they could have already. This changes nothing. (although this spat on /. might bring it to MS attention.)

    --
    I won't join Slashcott. OTOH, If Beta goes live, I just won't be back until it's fixed. Sorry Dice.