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

503 comments

  1. Frist by Ethanol-fueled · · Score: 4, Interesting

    TFA: "However, Microsoft says clearly that only Novell can supply Moonlight to end-users:".

    Rolling Mono (note: Mono != Moonlight) into Debian would be beneficial for both Debian and Microsoft. I don't believe that Microsoft will take legal action against Debian or Miguel, but it wouldn't surprise me in the least considering Microsoft's recent suicidal business divisions.

    1. Re:Frist by maxume · · Score: 5, Interesting

      It seems to me that, even if Microsoft threw a fit, the worst case scenario would be that they have to pull the package out of the releases.

      I suppose it might be a bigger deal for Canonical, but even the craziest judge isn't going to impose some ridiculous punishment for actions they take on good faith.

      --
      Nerd rage is the funniest rage.
    2. Re:Frist by eugene2k · · Score: 2, Interesting

      The biggest problem with this is that if mono is installed by default on systems that makes it more acceptable for ISVs to write their software for Mono/.NET which will hurt the (Debian or any other) platform if Microsoft suddenly decides to sue and Mono has to be removed.

      --
      Apple has "Mac vs PC", Microsoft has "Laptop Hunters", Linux has recession
    3. Re:Frist by vlm · · Score: 2, Interesting

      The biggest problem with this is that if mono is installed by default on systems that makes it more acceptable for ISVs to write their software for Mono/.NET which will hurt the (Debian or any other) platform if Microsoft suddenly decides to sue and Mono has to be removed.

      That would not hurt Debian very much, because Debian is really big and doing .NET stuff isn't a significant activity for Debian users... For example, currently the sum of .net use is a 50 meg "notepad" application, I think Debian will survive if that has to be removed.

      If it were removed, the ISVs that relied on it would be toast. From their perspective, not much has really changed, other than, possibly, temporarily, future Debian machines might have some version of mono/.net installed.

      --
      "Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
    4. Re:Frist by binarylarry · · Score: 1

      Microsoft doesn't need to sue. All they need to do is rattle the sabre and put the fear out there that they might begin to go after people.

      And Steve Ballmer has already said this option in on the table.

      --
      Mod me down, my New Earth Global Warmingist friends!
    5. Re:Frist by Actually,+I+do+RTFA · · Score: 1

      I don't believe that Microsoft will take legal action against Debian or Miguel, but it wouldn't surprise me in the least considering Microsoft's recent suicidal business divisions.

      What's mysterious about Microsoft's patent claims? They offered "fair and non-descriminary pricing" or what-have-you as a condition of getting .NET to be an ISO standard. Although not immediately obvious to me, I assume that's clear enough for someone out there to understand.

      --
      Your ad here. Ask me how!
    6. Re:Frist by shutdown+-p+now · · Score: 1

      Microsoft doesn't need to sue. All they need to do is rattle the sabre and put the fear out there that they might begin to go after people.

      And Steve Ballmer has already said this option in on the table.

      Well, Balmer said the option is on the table regarding Linux in general, not just Mono (remember "200 patents"?). Then there's also OpenOffice, Samba, Wine ... the list of potential targets is long, and Mono is by far not the most likely one on it. In fact, quite a few specs that Mono implements are under Open Specification Promise, which means no patent concerns.

      Anyway, did anyone really care about "200 patents" in Linux? If not, then why should anyone care any more about similar things in Mono? If

      If you want to hate it because it's Microsoft-designed tech, it's fine. But at least be consistent.

    7. Re:Frist by moniker127 · · Score: 1

      "Sir- the linux people's open sores have mono now."
      "What the kissing disease? Don't they know your not supposed to kiss sores, your supposed to bandage them?"
      "Apparently not sir. For some reason, there is talk that we will sue them for this."
      "I'm going to be honest, Roberts. I really do not fucking understand these people."

    8. Re:Frist by binarylarry · · Score: 2, Insightful

      Samba and Mono are the only technologies you listed that are an exact protocol/format/etc. clone of Microsoft's technology. Samba doesn't provide the strategic usefulness that Mono could if used widely in OSS.

      There's a better alternative anyway: Java. Of which the official implementation is open source and the IP/Patents involved are legal for general use.

      Whereas Microsoft's last words on the subject of Mono were that it's "an unauthorized reverse engineering of Microsoft intellectual property."

      --
      Mod me down, my New Earth Global Warmingist friends!
    9. Re:Frist by ultrabot · · Score: 2

      If you want to hate it because it's Microsoft-designed tech, it's fine. But at least be consistent.

      This probably summarizes the main concern.

      "Never truth Microsoft". Not much else needs to be said about this.

      You can deal with microsoft stuff if you thoroughly wash your hands after it. Samba is such a "realpolitik" project. But Mono, at times, seems like settling down at the Redmond sewers.

      Linux no longer needs to "desperately" co-operate with Microsoft - internet & web apps rewrote the game. This was not the case when Mono was conceived. Also, back in the day there was not much happening in the cross-platform landscape, whereas now everything is cross-platform (and Mono+Gtk# is an also-ran there).

      --
      Save your wrists today - switch to Dvorak
    10. Re:Frist by harlows_monkeys · · Score: 1

      I suppose it might be a bigger deal for Canonical, but even the craziest judge isn't going to impose some ridiculous punishment for actions they take on good faith

      Especially considering that one of the inventors on the relevant patent has publicly stated that the patent is available royalty free, as has the person in charge of IP at Microsoft. Estoppel would come into play now if Microsoft tried to charge royalties for the patent. So, even in the highly unlikely event that they were able to use the patent to stop any given free software implementation of their technology, it is almost inconceivable that there would be any monetary damages--just an order to stop distributing the technology. In that case, if there are significant apps using it, the patent would be worked around (just like open source developers plan to do for the numerous other patents violated in open source--which is also what those of us mostly working on closed source plan to do for all the patents we surely infringe).

    11. Re:Frist by Anonymous Coward · · Score: 0

      That would not hurt Debian very much, because Debian is really big and doing .NET stuff isn't a significant activity for Debian users...

      It must be significant enough to install it by default. Or planned to be significant.

    12. Re:Frist by Anonymous Coward · · Score: 0

      "I'm going to be honest, Roberts. I really do not fucking understand these people."

      "I'm going to be honest, Roberts. I really understand fucking these people.

      There, fixed that for you.

    13. Re:Frist by eugene2k · · Score: 1

      When Windows 95 came out - it also had just a notepad that worked on it. What would happen if the GUI libraries were replaced with different ones because of "licensing problems"? The OS would easily loose a huge market share, and those users would move to MacOS and Linux. Because since 1995 windows has grown from a platform with a notepad into this hugely popular platform with thousands of applications developed for it. And thousands of users are now using Windows just because of all those applications.

      If Mono is removed because of licensing issues, not only the ISVs that relied on it are toast, but also Debian and others whom Microsoft chooses will loose the users that relied on those .NET/Mono apps. And guess what platform those users will switch to?

      --
      Apple has "Mac vs PC", Microsoft has "Laptop Hunters", Linux has recession
    14. Re:Frist by Anonymous Coward · · Score: 0

      If Mono is removed because of licensing issues...

      It's not about mono being removed, it's about mono being included by default. Debian should just move mono and apps that depend on it out of main. That way, if the user wanted it, they could just select and install it themselves.

    15. Re:Frist by Schraegstrichpunkt · · Score: 1

      So, even in the highly unlikely event that they were able to use the patent to stop any given free software implementation of their technology, it is almost inconceivable that there would be any monetary damages--just an order to stop distributing the technology.

      "Just" an order to stop distributing the technology is a tad expensive if you're a hardware manufacturer. Like TomTom.

    16. Re:Frist by dudpixel · · Score: 1

      I dont even think it would go that far. Mono is just an API isn't it? its just wrapping the .NET API so that apps written for .NET can compile and run natively on Linux. So Mono isn't even remotely controlled by Microsoft. Microsoft controls .NET, and Mono follows behind of its own accord, implementing the changes to match .NET.

      If .NET disappeared, Mono would still work and so would all apps written for it.

      The worst that could happen is Microsoft could intentionally change .NET to break compatibility with Mono, but even so, that wouldn't break anything in gnome or even give MS any control over gnome. It would just make Mono a bit worthless until it caught up with .NET again.

      Is wine in the main repository? its a similar scenario.

      --
      This seemed like a reasonable sig at the time.
    17. Re:Frist by Yfrwlf · · Score: 1

      Saying "oh well it's OK because right now it doesn't hurt anyone too much...right now..." is just plain stupid. Get rid of it, the sooner the better, there's no need to go down that path and risk your programs. Build your programs on open and patent-free things, and help improve/design them if you can, but developing for Mono is developing on top of Microsoft again, you might as well be programming for Windows, and one of the reasons for going open source was to get away from Microsoft and their patent and closed software portfolios.

      Why play in their TNT-filled sandbox when you have an open world of possibilities outside it?

      --
      Promote true freedom - support standards and interoperability.
    18. Re:Frist by Yfrwlf · · Score: 1

      Not that, you know, you should support software patents...it's just they create headaches for anyone living in stupid countries.

      --
      Promote true freedom - support standards and interoperability.
    19. Re:Frist by Whitemice · · Score: 1

      *NO* "specifications patented by Microsoft and licensed under undisclosed terms" for use in Mono.

      This is just idiots confusing the M$/Novell deal with something to do with Mono, which is doesn't even relate to.

      --
      Using "Common Sense" is being either to arrogant or to ignorant to ask people who know more about something than you.
    20. Re:Frist by Whitemice · · Score: 1

      The biggest problem with this is that if mono is installed by default on systems that makes it more acceptable for ISVs to write their software for Mono/.NET

      Great, because there are allot of very good .NET applications and .NET is a very nice development platform.

      which will hurt the (Debian or any other) platform if Microsoft suddenly decides to sue and Mono has to be removed.

      *NO* "specifications patented by Microsoft and licensed under undisclosed terms" for use in Mono. A patent that applies to Mono almost certainly would equally apply to Java and very probably GCC.

      --
      Using "Common Sense" is being either to arrogant or to ignorant to ask people who know more about something than you.
    21. Re:Frist by Whitemice · · Score: 1

      If Mono is removed because of licensing issues...

      It's not about mono being removed, it's about mono being included by default. Debian should just move mono and apps that depend on it out of main.

      Why? Python is included in main. Any software patent that applies to Mono would very likely apply to Python as well.

      --
      Using "Common Sense" is being either to arrogant or to ignorant to ask people who know more about something than you.
    22. Re:Frist by Whitemice · · Score: 1

      Microsoft doesn't need to sue. All they need to do is rattle the sabre and put the fear out there that they might begin to go after people.

      Right, that is why so many companies with smart legal departments have no issue at all using Mono. Like IBM, Novell, Cannonical, a gillion gaming companies (yet Mono is huge in game development). Because all the non-lawyers here are clearly so much smarter than all their actual lawyers.

      --
      Using "Common Sense" is being either to arrogant or to ignorant to ask people who know more about something than you.
    23. Re:Frist by expat.iain · · Score: 1

      Mod parent up. The statements are factually correct in every way and should by no means be tagged as 'troll'.

      Both Samba and Mono are clones, although I would suggest that certainly Samba has better performance than native Windows machines.

      Java is removed from the IP/patent stone-round-the-neck negativity.

      A link to the Microsoft quote would be nice though.

      Iain.

    24. Re:Frist by Xabraxas · · Score: 1

      Whereas Microsoft's last words on the subject of Mono were that it's "an unauthorized reverse engineering of Microsoft intellectual property."

      I can't find that quote anywhere. Did you make it up? There is a similar quote made 8 years ago by an industry analyst but nothing like that coming from Microsoft. Considering Microsoft actively helped with getting Moonlight to version 1.0 I don't think it's accurate to describe Microsoft's intentions with a made up quote as opposed to their actions.

      --
      Time makes more converts than reason
    25. Re:Frist by Xabraxas · · Score: 1

      I dont even think it would go that far. Mono is just an API isn't it? its just wrapping the .NET API so that apps written for .NET can compile and run natively on Linux. So Mono isn't even remotely controlled by Microsoft. Microsoft controls .NET, and Mono follows behind of its own accord, implementing the changes to match .NET.

      That's not an accurate description. Mono isn't a .NET implementation. It is a C# + CLR implementation that has its own libraries. There is limited .NET compatiblity included but Linux applications in general do not use it. For example Tomboy uses GTK# not Windows.Forms. Mono doesn't need to "keep up" with .NET because most of the junk that has been added to .NET since around version 2.0 or so has been MS specific stuff that has no bearing on the C# language. In fact Mono has sprinted ahead of Microsoft in some areas.

      The worst that could happen is Microsoft could intentionally change .NET to break compatibility with Mono, but even so, that wouldn't break anything in gnome or even give MS any control over gnome. It would just make Mono a bit worthless until it caught up with .NET again.

      That's not even an issue because Linux applications that use Mono only really depend on the standarized language/libraries and not the Microsoft specific stuff. I guess it could be an issue if your goal is to create software that runs on both .NET and Mono but that actually rarely seems to be the case and certainly isn't the case with GNOME software based on Mono.

      --
      Time makes more converts than reason
    26. Re:Frist by binarylarry · · Score: 1

      No, I didn't make it up:

      http://searchwindevelopment.techtarget.com/news/article/0,289142,sid8_gci1019210,00.html

      I think it fits Microsoft's position and strategy perfectly. Of course they want to wait until it's the perfect time to act.

      You know, don't knife the baby until the opportune moment.

      --
      Mod me down, my New Earth Global Warmingist friends!
  2. Yay First Post by nscott89 · · Score: 0, Offtopic

    I see Microsoft having a field day with this...

    1. Re:Yay First Post by Dan+Ost · · Score: 1

      What, exactly, is Microsoft going to do with this information?

      --

      *sigh* back to work...
    2. Re:Yay First Post by Anonymous Coward · · Score: 0

      They don't even know they're stupid!

  3. 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 Anonymous Coward · · Score: 1, Insightful

      I'm removing Tomboy from my fedora 11 install as we speak.

      I never use it and it just sucks up resources.

    2. Re:Call Upon the ECMA Code of Conduct by Ethanol-fueled · · Score: 3, Informative

      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.

    3. 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?"
    4. Re:Call Upon the ECMA Code of Conduct by TheRealMindChild · · Score: 5, Interesting

      Did you read their patent claim? If you closed your eyes, had someone else read it to you, and you had no idea the company of which it came from, you would swear it was a Sun patent on Java/SOAP.

      --

      "When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
    5. Re:Call Upon the ECMA Code of Conduct by EvilIdler · · Score: 5, Informative

      I guess Tomboy is a nice test-case. But all that junk to install just for a note-taking program? Also, wouldn't it be nice if the Slashdot summary told me what Tomboy does?

      The project page is a little more informative:
      http://freshmeat.net/projects/tomboy

    6. Re:Call Upon the ECMA Code of Conduct by wisty · · Score: 1

      Shouldn't patents be non-obvious, but easy to implement for a skilled professional in the field?

      I though that XML web services were pretty obvious (given XML-RPC, SOAP, and every other web framework on the planet), but the difficulty in creating such a framework would be in the implementation.

    7. Re:Call Upon the ECMA Code of Conduct by ketilwaa · · Score: 3, Funny

      I just did an apt-get update on my Ubuntu install. Right before, I checked my e-mail. Does any other slashdotters have nice anecdotes from their computing day? Has anyone opened a document or did a uname or anything that will interest us? I'll be waiting!

    8. Re:Call Upon the ECMA Code of Conduct by Chrisq · · Score: 1

      You disgust me, she's been dead for ten years now.

    9. 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.
    10. Re:Call Upon the ECMA Code of Conduct by recoiledsnake · · Score: 1

      I guess Tomboy is a nice test-case. But all that junk to install just for a note-taking program?

      Tomboy is not 50MB, the whole Mono framework is that much, Tomboy is relatively small. If you use F-Spot or Beagle, Mono runtime is installed anyway. Debian had reason to include Tomboy instead of Gnote. Also Tomboy does not have Applet support, which is why Debian wants it in the Gnome install instead of Gnote. From http://www.archivum.info/fedora-desktop-list@redhat.com/2009-04/msg00005.html [archivum.info] :

      - We're using tomboy as an applet, which gnote currently does not support. I'm far from a notification area purist, but I do think that a note-taking application has no place in it... - If we are talking about replacing tomboy with gnote, we need to have some data migration that is more automatic that 'open terminal, cp .tomboy .gnote'. - While gnote on the surface looks like a clone of tomboy, if you look at the addins that come with tomboy, you'll probably find that gnote is not yet a full replacement for tomboy power users (it certainly works fine for my tomboy use...).

      --
      This space for rent.
    11. Re:Call Upon the ECMA Code of Conduct by Anonymous Coward · · Score: 1, Insightful

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

      Well that might have been the original reason, but it doesn't mean that once that reason is removed there's no purpose.

      Ubuntu's bug #1 is that microsoft have a monopoly. If microsoft closed it's doors you wouldn't say "Oh well that's that, let's stop this ubuntu thing.".

    12. Re:Call Upon the ECMA Code of Conduct by segedunum · · Score: 2, Interesting

      Read the detail at the bottom behind the claims they're making. It becomes clear that they are ring-fencing certain APIs in any CLR compatible implementation mainly to do with web services but also APIs that seem to be essential to get a working CLR, but are not in the ECMA specifications. Implement ECMA and you basically have something akin to Rotor, which does pretty much nothing.

    13. Re:Call Upon the ECMA Code of Conduct by Qubit · · Score: 1

      Were I a Debian leader, I would simply approach Microsoft with the Mono code and the ECMA code of conduct [ecma-international.org] and demand it in writing that for this snapshot of the code you have a forever royalty free to interact with .NET.

      What if someone wants to fix a bug in Mono or update it? Licenses that only cover snapshots of code or certain signed binaries are probably more of a headache than having no license at all. At least in the latter case you're less likely to have users be deluded into thinking that they're legally covered.

      --

      coding is life /* the rest is */
    14. Re:Call Upon the ECMA Code of Conduct by Anonymous Coward · · Score: 0

      And that is a problem, why? Ah, that's right, you and your provincial attitudes about sex, requiring a pulse and everything. You must be an American to be so backward.

    15. Re:Call Upon the ECMA Code of Conduct by EvanED · · Score: 1

      Or they've already gotten him.

      If Miguel is distributing parts of Mono copyrighted by other people knowing that a patent license is required to use it, he's in violation of the GPL and violating those contributors' copyrights.

      (I'm not sure if Mono requires copyright assignment for contribution.)

    16. Re:Call Upon the ECMA Code of Conduct by Anonymous Coward · · Score: 1, Insightful

      *On another note: What's the point of Gnome again, now that Qt/KDE is open sourced?*

      To not be a cluttered piece of crap, which is KDE's job. See on UNIX, every program should do one thing and do it well.

    17. Re:Call Upon the ECMA Code of Conduct by Hatta · · Score: 5, Informative

      Tomboy is not 50MB, the whole Mono framework is that much, Tomboy is relatively small. If you use F-Spot or Beagle, Mono runtime is installed anyway.

      And if you dont(most people), it's not installed. It's available in the repositories if you want it, why crap it into the base install?

      Debian had reason to include Tomboy instead of Gnote. Also Tomboy does not have Applet support, which is why Debian wants it in the Gnome install instead of Gnote

      Gnote 0.3.0 released 2009-04-29 adds applet support. Why use Tomboy at all now?

      --
      Give me Classic Slashdot or give me death!
    18. Re:Call Upon the ECMA Code of Conduct by Ed+Avis · · Score: 1

      All non-trivial software implements patents, some of which are held by companies we dislike. Why give Microsoft a power of veto over what software is included in Debian? You could equally well present them with a printout of the Linux kernel source and ask them to promise not to assert any patents they hold that cover it (even if the claim of "283 software patents" is not substantiated, they must still have quite a few). I find this attitude, that you can't write or package any software without asking Microsoft for permission, extremely strange. (Is VFAT long filename support included in Debian's standard kernel?) The Wine project has no such qualms, and nor does Samba.

      --
      -- Ed Avis ed@membled.com
    19. Re:Call Upon the ECMA Code of Conduct by Anonymous Coward · · Score: 3, Insightful

      Thing is, though, those nice UNIXy console programs often have a lot of optional parameters, because there are subtle details in doing something well. They are defaulted to sane values, because you don't usually need them, but when you do need them, it wouldn't be trivial to work around not having them.

      What you call clutter on KDE is what an advanced user can use to optimize their workflow. The problem with Gnome apps is that they toss all those advanced options away. Not just hide them in a "Here be dragons" advanced options menu with sane defaults, but totally removed. And that cuts badly into their usability relative to KDE apps once you're past the training wheels level of skill.

    20. Re:Call Upon the ECMA Code of Conduct by LizardKing · · Score: 1

      Does any other slashdotters have nice anecdotes from their computing day?

      Well, I've just taken a dump as I'm about to go home, and as our DBA says there's nothing quite as satisfying as logging out while still on company time.

    21. Re:Call Upon the ECMA Code of Conduct by Anonymous Coward · · Score: 0

      Because Tomboy has more than one developer (and thatâ(TM)s by far reason #1).
      Because Tomboy has support for synchronization.
      Because Tomboy is translated into 3 times as many languages.
      Because Tomboy is the official choice of GNOME.
      And last but not least, because there are so many uninformed trolls complaining about it, itâ(TM)s so funny seeing them struggle for such a stupid reason.

    22. Re:Call Upon the ECMA Code of Conduct by setagllib · · Score: 1

      Real men use aptitude.

      --
      Sam ty sig.
    23. Re:Call Upon the ECMA Code of Conduct by krasmussen · · Score: 1

      Tomboy is the app I would, in all seriousness, put as #1 on my list of Linux killer apps.

      Oh, and it's a note-taking program with wiki-style linking between notes, among other things. It pulls thoughts right out of my brain and makes it trivial to organize and retrieve them later on.

    24. Re:Call Upon the ECMA Code of Conduct by Anonymous Coward · · Score: 0

      Yeah, and Obama shot Kennedy from the grassy knoll. Make sure your tinfoil hat is shiny side out!

    25. Re:Call Upon the ECMA Code of Conduct by Anonymous Coward · · Score: 0

      To not be a cluttered piece of crap, which is KDE's job.

      Right, that'd be why Gnome is pulling in a 50MB package.

    26. Re:Call Upon the ECMA Code of Conduct by Schraegstrichpunkt · · Score: 1

      Don't be so daft. If Microsoft's past behaviour is any indication, they wouldn't sue Debian. They'd sue individual Debian users and distributors. Look at what they did to TomTom.

      Microsoft's strategy seems to be to make "FOSS" and "non-commercial" equivalent. Part of this strategy is to treat "commercial" and "open source" as a dichotomy in all their PR materials, and part of this strategy is to scare anyone who dares to use FOSS commercially.

    27. Re:Call Upon the ECMA Code of Conduct by Anonymous Coward · · Score: 0

      Shouldn't patents be non-obvious, but easy to implement for a skilled professional in the field?

      I don't know where you got "easy to implement" part from, if you remove it from the sentence it will be the patent law I know "Patents must be non-obvious to a skilled professional in the field".

    28. Re:Call Upon the ECMA Code of Conduct by Ilgaz · · Score: 1

      The cluttered OS you talk about is modeled after the Framework idea and especially re-usable code.

      It should be the ''what app should achieve'' instead of the entire GUI etc.

      With KDE4, they have even went closer to the real vision and KDE 4 runs in all operating systems, all guis, natively without any hacks. It is the actual idea of NeXT which had to get shaved down because Apple purchased them, they have a hardware business etc.

      So dear AC, my equally ''bulky'' OS X built around the very same object oriented idea is way bigger than your monkey boy's Gnome. OS X reached 10% in desktop share and some amazing number on mobile share. Which idea was right? Lets speak when Nokia smart devices come with KDE installed, should we?

    29. Re:Call Upon the ECMA Code of Conduct by Ilgaz · · Score: 1

      Do you know why I stay away from Gnome even while I have option to run and install it on OS X?

      There are some central functionality applications coded by the Gnome camp which requires Mono, that trojan (in my eyes) to compile and function. I think Icaza and the gang somehow convinced them without bothering to explain WHY they have to use Microsoft .NET rather than being poster child of MS intention to multiplatform (heh really!).

      Less politely, they are sold out in my eyes and I won't put a byte of MS code on a Windows free environment. I run OS X and I shouldn't have to. Except the fonts Apple paid them for inclusion in OS X which amazingly breaks font rendering in some browsers.

      I think Linux users should ask themselves about the decision they made when they reject free (somehow) Windows and install Linux and act accordingly.

      At least, Windows users can read some EULA. In Mono case, it is undisclosed terms.

      You guys aren't Novell going chapter 11 soon so have to deal with the devil... If you use Linux, use the real thing without trojans and soon to be trojaned desktops.

    30. Re:Call Upon the ECMA Code of Conduct by Hurricane78 · · Score: 1

      Aah, now I get where your POV comes from. And I agree totally to the unix philosophy.

      But there is not a single desktop environment on this planet, who actually does this. For this, the buttons in an application for example, would have to be separate programs.

      But just removing functions, while still going completely in the opposite direction than the UNIX philosophy, is even worse than putting them all in large monolithic apps.

      Besides: The KDE core apps are not that monolithic at all. Hell, even the "K-Menu" is a different app from the task bar. And Plasma is specifically made to go in the direction of the UNIX philosophy. People just don't get it, because of horrible marketing. and developers think they can just fit their old apps into the new thing, and be done. Instead of splitting them up.

      About the options: Options are equivalent to freedom and individuality. If you call that "cluttered crap", then no wonder totalitarian "one law to rule them all" governments are on the rise.
      The point that apparently nobody gets, is that you offer as much options as possible but you set sensible defaults. So if you just imagine there is no "Settings" menu option, you got your Gnome. and if you use it, then you got you KDE. Or everything else in between.
      I also recommend profiles. Even hierarchical cross-application profiles, that you can download from a site like kde-profiles.org or something like that.

      --
      Any sufficiently advanced intelligence is indistinguishable from stupidity.
    31. Re:Call Upon the ECMA Code of Conduct by Abcd1234 · · Score: 1

      Why use Tomboy at all? I much prefer WikidPad. Portable Python, can be installed on a USB key, the wiki's can be easily revision controlled (mine is squirreled away in a Git repository)... works great for me!

    32. Re:Call Upon the ECMA Code of Conduct by Xabraxas · · Score: 1

      Qt is over 100MB. Does that make KDE more bloated then?

      --
      Time makes more converts than reason
    33. Re:Call Upon the ECMA Code of Conduct by Abcd1234 · · Score: 1

      You keep saying that, and yet you're still wrong, no matter how many times you repeat it.

      That patent doesn't just apply to .NET. They use .NET as an example of an API as described in the claims section. But the claims apply to *any API* on *any application stack* that implements said claims. Why do I say that? Because:

      a) the claims section makes no reference to .NET and it's the claims that outline the coverage of the patent... everything else is window dressing to clarify the intent of the claims, and
      b) every place where .NET is mentioned, it's a caveat to a more general statement. eg:

      "[0029] This disclosure addresses an application program interface (API) for a network platform upon which developers can build Web applications and services. More particularly, an exemplary API is described for the .NET.TM. platform created by Microsoft Corporation. "

      So the disclosure addresses an API. Period. Oh, and BTW, here's an example, it's described in .NET.

      So, while you may not like that said patent applies to deploying certain types of web applications on .NET, it also applies to any other language that implements the "invention" described in those claims.

      Meanwhile, you Mono/patent trolls have yet to cite single additional patent over and above this one... and this one doesn't cover just .NET. So if you're that concerned about this single, solitary patent, you better start opening up talks with the developers of all those other web development frameworks out there.

    34. Re:Call Upon the ECMA Code of Conduct by segedunum · · Score: 1

      You keep saying that, and yet you're still wrong, no matter how many times you repeat it. That patent doesn't just apply to .NET. They use .NET as an example of an API

      YES, it is. They are providing a background as to what their claims apply to. That amount of detail is not given as an example or merely as window dressing. Web services amongst other essential APIs in .Net IS what they are describing.

      a) the claims section makes no reference to .NET and it's the claims that outline the coverage of the patent...

      It doesn't matter. The detail section expands on what they mean regarding their claims, and they describe the API and namespaces in detail there. You only have to look at the abstract to see what it means:

      An application program interface (API) provides a set of functions for application developers who build Web applications on Microsoft Corporation's .NET.TM. platform.

      Meanwhile, you Mono/patent trolls have yet to cite single additional patent over and above this one...

      Running around shouting "Show me a patent!" isn't good enough. We should have learned it isn't good enough by now. An explicit patent waiver made public is all that is required, and yet the Mono proponent trolls still want to cover this up for Microsoft with non-existent letters and smoke and mirrors postings on mailing lists.

    35. Re:Call Upon the ECMA Code of Conduct by Abcd1234 · · Score: 1

      Running around shouting "Show me a patent!" isn't good enough.

      Yes, it is. Unless MS has filed patents, they can't go and retroactively request patents on material they've already published. That's the way the system works. Go look up "defensive publication". In short: once something has been divulged, unless a patent has been filed, it's no longer patentable.

      As such, anything described in the CLR that hasn't had a patent filed on it *can't be patented*. Otherwise, MS could just file patents on any random invention they come across in the wild. But they don't, because they can't.

    36. Re:Call Upon the ECMA Code of Conduct by renoX · · Score: 1

      >Rambus was chastised for their actions (like the linked article states).

      Chastised??? You should read better the article: the FTC tried but *failed* to do it and Rambus got a lot of money thanks to their 'submarine patents'.

      As for the rest, given their history (even recent one with OOXML), I don't understand how anybody could trust Microsoft..

    37. Re:Call Upon the ECMA Code of Conduct by segedunum · · Score: 1

      Yes, it is. Unless MS has filed patents, they can't go and retroactively request patents on material they've already published.

      It's all speculation, smoke and mirrors as to what might happen and is simply not borne out by what's happened with the abuse of the patent system over the past few years. An explicit and publicly available patent waiver like those made available by Google and even Sun so everyone knows the score could solve this in seconds. Anything else is just outright speculation that merits no discussion because there can be no resolution.

    38. Re:Call Upon the ECMA Code of Conduct by Abcd1234 · · Score: 1

      Ah, I see. So I point out a blatant hole in your paranoid theories (that you can't patent an already-published invention), and suddenly it's "just outright speculation",

      Interesting.

      Something tells me, no matter what MS did, you'd never be satisfied. If they published a waiver, you'd pick apart the text and come up with a wild theory about how MS could work around it.

      Meanwhile, I don't see you fighting the good fight against the kernel, X, or any number of other pieces of software that almost certainly violate *someone's* patents. And real patents, too. Not fictitious, future patents. Why is that, exactly? I mean, it couldn't be that, deep down, you just have issues with MS as a corporation, could it?

  4. Default installation? by Hatta · · Score: 5, Informative

    Last I checked, the "default installation" of Debian didn't even include X. So I'm guessing what they really mean is that they've included it in the default repositories, and if you apt-get gnome you'll get tomboy and mono too.

    --
    Give me Classic Slashdot or give me death!
    1. Re:Default installation? by Norsefire · · Score: 4, Funny
      Did you figure that out all by yourself, or did you do something as unslashdot-like as read the summary?

      OS News reports that Debian developer Josselin Mouette got Tomboy accepted as a dependency for gnome

    2. Re:Default installation? by Anonymous Coward · · Score: 0, Interesting

      Sorry, but you are wrong. The default install nowadays includes everything, including Gnome, and you need to go into super duper expert mode to get debian-base.
      This means Tomboy and Mono will squeeze into default Debian installs as soon as the current unstable hits release in 2020 or so.

    3. Re:Default installation? by isama · · Score: 1

      Debian never releases unstables. they go from unstable -> testing -> stable.

      Trolls don't even know what they are trolling about anymore these days... It makes me sad.

    4. Re:Default installation? by Anonymous Coward · · Score: 0

      Logic? Having gnome depend on tomboy depend on mono does not imply that mono is not in the default install.

    5. Re:Default installation? by Anonymous Coward · · Score: 0

      The packages that are now in unstable will "all" move to stable. How is that different from releasing "unstable"? The workflow doesn't change the facts. It's different with experimental. Unstable is what stable will look like in 10+-9 years. Mono will be there waiting for you.

    6. Re:Default installation? by machine321 · · Score: 1

      I'm not a Debian user, and my assumption from reading the summary was that Debian includes Gnome, and that Debian now had Mono "installed by default".

    7. Re:Default installation? by Maxwell42 · · Score: 3, Insightful
      Did you read the title the gp was referring to ?

      Mono Squeezed Into Debian Default Installation

    8. Re:Default installation? by Anonymous Coward · · Score: 0

      'Default installation' means desktop in this case, i.e. the desktop & gnome-desktop tasks.

    9. Re:Default installation? by fast+turtle · · Score: 1

      which is one more reason I hate Gnome and use either KDE or one of the lightweight WM's like fluxbox/FVWM

      --
      Mod me up/Mod me down: I wont frown as I've no crown
    10. Re:Default installation? by Anonymous Coward · · Score: 0

      The packages that are now in unstable will "all" move to stable. How is that different from releasing "unstable"? The workflow doesn't change the facts. It's different with experimental. Unstable is what stable will look like in 10+-9 years. Mono will be there waiting for you.

      Wow. The ignorance you display is incredible.

      Packages stay in unstable only long enough to work out that major bugs and are then moved to testing where the the rest of the bugs are then removed through the expanded user base. Many packages are there for a few weeks. The only ones that stay there for any extended period of time are the ones that require major upgrades to the system libraries such as libc, or to something such as udev, etc... thus taking longer as the entire Debian system needs upgrading before they will have their dependencies resolved.

      That means it is possible for a package to move from unstable to stable in a matter of months, if it enters unstable just before a freeze on testing, and doesn't require huge changes to the rest of the system. The most time a package would take is about 2-3 years, based on Debian's normal release schedule, and it would be brought up-to-date during its stay in both unstable and testing.

      If a person runs testing they normally have newer software packages than they would running Ubuntu and upgrading it at every release. IOW's Debian testing is a very up-to-date distribution, and I find it to be far less buggy than new Ubuntu releases.

    11. Re:Default installation? by MrHanky · · Score: 1

      I find it amazing that more than two moderators think this comment should be modded up. Hint: everything parent says is wrong.

    12. Re:Default installation? by Anonymous Coward · · Score: 0

      I've modified my Adblock to not only block ads, but summaries too :)

    13. Re:Default installation? by mcubed · · Score: 1

      Using the netinstall CD, GNOME is installed if you select the desktop environment option from the task list the installer presents you with. If you don't select that task, GNOME is not installed. On this score, all install modes (expert or standard) are the same. It's easy not to install GNOME if you don't want to install GNOME.

      --
      "No live organism can continue for long to exist sanely under conditions of absolute reality;..."
    14. Re:Default installation? by grimdonkey · · Score: 1

      Last I checked, the "default installation" of Debian didn't even include X.

      When did you last check? 1995?

    15. Re:Default installation? by Carewolf · · Score: 1

      Debian doesn't have a default desktop, so default installation in this case means the user actively selects and installs GNOME.

    16. Re:Default installation? by VulpesFoxnik · · Score: 1

      Don't Forget XFCE4.

      --
      RES PUBLICA NON DOMINETUR
    17. Re:Default installation? by VulpesFoxnik · · Score: 1

      There is a command line parameter called "desktop" you can use, in addition the new ne-tinstall CDs now have a menu option for selecting them. It's documented in the help section of the installer.

      --
      RES PUBLICA NON DOMINETUR
    18. Re:Default installation? by Anonymous Coward · · Score: 0

      Unstable is what stable will look like in 10+-9 years. Mono will be there waiting for you.

      So 2010?

    19. Re:Default installation? by jonnyt886 · · Score: 1

      Did you figure that out all by yourself, or did you do something as unslashdot-like as read the summary?

      Did you figure that out all by yourself, or did you do something as unslashdot-like as read the title ?

      Mono Squeezed Into Debian Default Installation

  5. 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 vintagepc · · Score: 3, Insightful

      People on Dial-up cringing as they read that?

      --
      Evolution - Est. 4500000000 B.C. Don't piss in the gene pool.
    2. Re:Incredible horrifying bloat by Freetardo+Jones · · Score: 4, Informative

      What's wrong with this picture?

      You mean other than the fact that the statement is bullshit? I have a compiled version of Tomboy and it only comes out to around 5-6 megs. The 50MB size is them including all of it's secondary dependencies (which are used by other programs as well) to create a completely misleading picture.

    3. Re:Incredible horrifying bloat by hattig · · Score: 2, Interesting

      Is TomBoy built upon Mono? I've used it - it's a terrible unusable bit of software that acts entirely counter-intuitively for taking notes, with a GUI that is neither compact or usable for managing the notes.

      Someone could rewrite it in native GTK/Gnome/SQLite in a few days I'm sure.

      Seriously, the old "note dock" applet for WindowMaker was better, and that was 12 years ago.

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

    5. 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
    6. Re:Incredible horrifying bloat by Bob54321 · · Score: 4, Informative

      Look for GNotes. It is Tomboy ported to C++. That has annoyed to Tomboy developers....

      --
      :(){ :|:& };:
    7. Re:Incredible horrifying bloat by tepples · · Score: 3, Insightful

      I have a compiled version of Tomboy and it only comes out to around 5-6 megs.

      A 20 minute download for a note-taking app?

      The 50MB size is them including all of it's secondary dependencies (which are used by other programs as well)

      Used by other programs, true, but not necessarily those included as a dependency for the "typical" Debian desktop install.

    8. Re:Incredible horrifying bloat by Freetardo+Jones · · Score: 1

      We can't expect small, lean applications written in C# because of the language's design.

      That's amusing since I've written many applications in C# that are small and lean. I've ported a number of applications to C# that have a compiled binary that is usually no more than 10-15% larger than the C/C++ program. But no, it must be the language's fault not the incompetent programmers using it because clearly no one can write bloated, memory-hungry, slow C or C++ applications. Oh wait...

    9. Re:Incredible horrifying bloat by Freetardo+Jones · · Score: 1

      A 20 minute download for a note-taking app?

      20 minutes? I downloaded the source tarball in 10 seconds.

      Used by other programs, true, but not necessarily those included as a dependency for the "typical" Debian desktop install.

      Yes, but you never see anyone include the glibc, alsa, etc dependencies when they give you the size of a C/C++ program. In this case it was just used to create a hugely overinflated figure.

    10. Re:Incredible horrifying bloat by Vexorian · · Score: 3, Insightful

      (which are used by other programs as well)

      Except these other programs are not included as a gnome dependency...

      --

      Copyright infringement is "piracy" in the same way DRM is "consumer rape"
    11. Re:Incredible horrifying bloat by Darkness404 · · Score: 1

      A 20 minute download for a note-taking app?

      I don't know what internet connection you are on, but 50 MBs only takes 5-10 minutes on my pathetically slow DSL connection. If you mean the 6 MB that only takes a minute or two at most.

      But, you don't seem to get the idea of dependencies. To put it with a different language, you are complaining that a program coded in Java requires a Java VM to run, or that a program coded in python requires a python interpreter.

      --
      Taxation is legalized theft, no more, no less.
    12. Re:Incredible horrifying bloat by Freetardo+Jones · · Score: 1

      Maybe not in Debian because it excludes them but a whole host of other default gnome apps do share it. The fact of the matter is you never see anyone include the sizes of glibc, alsa libs, or any other dependencies (many of which can amount to quite a few megs themselves) when someone talks about any C/C++ application. But whenever a C# app is talked about all of it's dependencies are included on top of the size of the app to create a wildly misleading picture.

    13. Re:Incredible horrifying bloat by hattig · · Score: 3, Insightful

      Cheers. I see no reason therefore to include Tomboy + Mono by default with Gnome on Debian - or do other parts of Gnome depend upon Mono now?

    14. Re:Incredible horrifying bloat by recoiledsnake · · Score: 4, Informative

      Gnote is a line by line clone of Tomboy from C# to C++. Even the GUI is exactly the same. Don't believe me? See the screenshots at http://robertmh.wordpress.com/2009/06/12/mono-in-the-default-install/ So his complaints would all be still valid, unless he's biased against mono.

      --
      This space for rent.
    15. Re:Incredible horrifying bloat by Freetardo+Jones · · Score: 1

      The most positive description I could give a C# "application" is quick and dirty.

      Then you don't use it much. This is what most people say that have nothing but a cursory glance at the language or have never actually used it.

      I put application in quotes because calling something written in a scripting language anything other than a script, IMHO, is annoying.

      C# isn't a scripting language. You clearly don't know what a scripting language is to make such a laughable statement.

      The fact that the script needs to be accompanied by so much extra baggage, mono, it can not be considered small or lean.

      Because no C/C++ application is accompanied by extra baggage? I guess I must be dreaming every time I download one of them and have to download 5-10+ megs of dependencies when I apt-get one.

    16. Re:Incredible horrifying bloat by FudRucker · · Score: 1

      i agree with the original poster that Tomboy & its dependencies are an incredible mess, what happened to the unix philosophy of KISS? well ./Debian/Gnome/Mono/Tomboy can kiss my ass!

      i would rather use a pencil & paper, just think pencil & paper does not require electricity or even a computer, but if i did want to store electronic information i would use somethhing a lot more simpler, vi, or leafpad, these Linux desktops [eg] gnome/kde4 have lost their way, they no longer represent what Linux was supposed to be, fuck em...

      --
      Politics is Treachery, Religion is Brainwashing
    17. Re:Incredible horrifying bloat by ubersoldat2k7 · · Score: 3, Insightful

      You see, Linux/Unix/BSD don't need Mono! What can you achieve using Mono which you wouldn't achieve with Perl, Python, C++ or Java? Name one, please, only one. Linux already have great software tools, great programming languages and great graphical libraries. Why are this guys, which I believe have their best of interests, trying to shove up our asses a lame excuse of a programming language that basically doesn't bring anything new but license agreements, EULAs, patents to a perfectly, usable environment? I see why Microsoft needs .Net and C#, they have nothing better to offer to their clients, but come on. And yes, only the mono-runtime package consumes 27MB of space. For what? For Tomboy? I can code a Tomboy like app in Python in three days... come on!!!

    18. Re:Incredible horrifying bloat by ketilwaa · · Score: 1

      It is not a line by line clone. A small count: Tomboy has 13 addons that comes with the app, Gnote has 6. For one, Gnote does not have any synchronization addons.

    19. Re:Incredible horrifying bloat by recoiledsnake · · Score: 1

      It is not a line by line clone. A small count: Tomboy has 13 addons that comes with the app, Gnote has 6. For one, Gnote does not have any synchronization addons.

      Uh? How does the lack of synchronization addons mean that it's not a clone? Synchronization code is being worked upon, according to Gnote's site. From http://www2.apebox.org/wordpress/rants/93/

      Gnote is, for those living under a large pile of particularly non-porous rocks, a fork of Tomboy, doing a line-by-line translation of the source into C++.

      Can you quote your source for claiming that it's not a line by line clone?

      --
      This space for rent.
    20. Re:Incredible horrifying bloat by ketilwaa · · Score: 0, Troll

      If it lacks some features it is hardly a line by line clone, is it? The source for my claim can easily be your acceptance of the fact that Tomboy has features that Gnote is lacking. The fact that someone is working on it doesn't mean anythin, the feature simply isn't there for me to use.

      Judging an app by what it *might* do in the future is hardly a good procedure for including the app in a default install. If Gnote is the better app in the future, then, by all means, substitute the two.

    21. Re:Incredible horrifying bloat by Anonymous Coward · · Score: 2, Insightful

      Tomboy pulls in a lot of dependencies that aren't used by anything else in the default Gnome desktop on Debian. I have only an Ubuntu machine to check this against (which already has Tomboy installed by default), but it looks like it's going to drag in:

      Mono runtime, and basic libraries (mono-runtime, mono-2.0-runtime, mono-gac, mono-2.0-gac, mono-jit, mono-common, libmono-corlib2.0-cil, libmono-security2.0-cil)
      Mono's Gnome libraries (libgconf2.24-cil, libglib2.0-cil, libgmime2.2a-cil, libgnome-2.24-cil, libgnome-panel2.24-cil, libgtk2.0-cil, libmono-addins-gui0.2-cil, libmono-addins0.2-cil, libmono-cairo2.0-cil, libmono-posix2.0-cil, libmono-system2.0-cil, libndesk-dbus-glib1.0-cil, libndesk-dbus1.0-cil)

      On the positive side, that's not installing everything that's usually bundled with Mono (or with Microsoft's .NET Framework, come to think of it). Thanks to Debian's packaging of Mono, this is only installing the subset of the libraries than Tomboy actually needs, so it's nowhere near as bad as it could be.

      It's still a lot of packages to pull in just to support one application. Especially an application which has a native-code port with at least equal features (GNotes), and which most people will never use anyway.

    22. Re:Incredible horrifying bloat by Anonymous Coward · · Score: 0

      > Why are this guys, which I believe have their best of interests,

      read the bug reports and do a search on Josselin's name for yourself.

      After doing that personally I wouldn't be so kind. He's just a self-aggrandizing prick who could give a rat's ass about the greater project and has only brought it pain.

    23. Re:Incredible horrifying bloat by Anonymous Coward · · Score: 0

      Just as you don't need java, python or perl.

    24. Re:Incredible horrifying bloat by recoiledsnake · · Score: 1

      Cheers. I see no reason therefore to include Tomboy + Mono by default with Gnome on Debian - or do other parts of Gnome depend upon Mono now?

      There ARE reasons, why not listen to the distro maintainers instead of armchair speculation from reading Slashdot posts? http://www.archivum.info/fedora-desktop-list@redhat.com/2009-04/msg00005.html [archivum.info] [archivum.info] :

      - We're using tomboy as an applet, which gnote currently does not support. I'm far from a notification area purist, but I do think that a note-taking application has no place in it... - If we are talking about replacing tomboy with gnote, we need to have some data migration that is more automatic that 'open terminal, cp .tomboy .gnote'. - While gnote on the surface looks like a clone of tomboy, if you look at the addins that come with tomboy, you'll probably find that gnote is not yet a full replacement for tomboy power users (it certainly works fine for my tomboy use...).

      --
      This space for rent.
    25. Re:Incredible horrifying bloat by lastman71 · · Score: 1

      Mono is required by other programs too?

    26. Re:Incredible horrifying bloat by Anonymous Coward · · Score: 0

      Yeah, and that python? Who needs that? Just wasted space! And don't let me get started on perl or, shudder, ruby!

    27. Re:Incredible horrifying bloat by recoiledsnake · · Score: 1

      If it lacks some features it is hardly a line by line clone, is it? The source for my claim can easily be your acceptance of the fact that Tomboy has features that Gnote is lacking. The fact that someone is working on it doesn't mean anythin, the feature simply isn't there for me to use.

      Judging an app by what it *might* do in the future is hardly a good procedure for including the app in a default install. If Gnote is the better app in the future, then, by all means, substitute the two.

      I simply don't get you, can't a line by line copy be incomplete because not all the lines were ported? What about integration issues with addons written in C# ? Won't that explain the lack of all addons? Either you're trolling and/or arguing just for the sake of it after realizing that you lost the argument. I am going to have to stop replying to you at this rate.

      --
      This space for rent.
    28. Re:Incredible horrifying bloat by recoiledsnake · · Score: 2, Informative
      From http://www.figuiere.net/hub/blog/?2009/04/06/657-gnote-010 [figuiere.net] See first comment by a Fedora maintainer:

      Monday 6 April 2009 15:39, by Rahul Sundaram :: # For Fedora, we had to remove tomboy from the live cd due to lack of space. Unfortunately, Gnote probably won't be a good replacement since it would pull in the gtkmm, boost and other dependencies. Have you considered Vala or PyGTK instead? So the summary includes the dependencies for Tomboy but not for Gnote. If you add up gtkmm and boost and other dependencies, it might get close to 50MB. The summary is a troll for comparing apples to oranges.

      --
      This space for rent.
    29. Re:Incredible horrifying bloat by ketilwaa · · Score: 1

      You wrote: "Gnote is a line by line clone of Tomboy from C# to C++. Even the GUI is exactly the same."
      It is not. Tomboy offers features that Gnote does not. The fact that an actual clone is worked upon does not mean it's here. You are telling me Gnote is incomplete, which it is. The reasons for lacking features are largely irrelevant to the user.

    30. Re:Incredible horrifying bloat by recoiledsnake · · Score: 1
      From your own post:

      It is not a line by line clone. A small count: Tomboy has 13 addons that comes with the app, Gnote has 6. For one, Gnote does not have any synchronization addons.

      So if I do a line by line cloning of Firefox into C#, and Adblock doesn't run on my clone because it's in C/C++ whatever and not in C# does that mean that my C# port was not a line by line clone?

      --
      This space for rent.
    31. Re:Incredible horrifying bloat by gbjbaanb · · Score: 1

      add-ons, by definition, are not part of the application. Therefore GNote may well be a line-by-line port of Tomboy. Nobody said anything about also porting any addons that may be available.

    32. Re:Incredible horrifying bloat by Tom9729 · · Score: 3, Informative

      You never see anyone include the sizes of dependencies like glibc, alsa, etc because they are pretty common across all applications. I mean honestly, find me a application that doesn't in some way depend on libc and I will be impressed.

      The reason the size of all of a Mono app's dependencies are included is because they are only useful for running Mono apps.

      In this case it is reasonable to include the size of Tomboy's dependencies because (so far) it is the only Debian-Gnome-required app that needs them.

    33. Re:Incredible horrifying bloat by Anonymous Coward · · Score: 0

      ...and don't forget that mono depends on glibc, alsa etc. too.

    34. Re:Incredible horrifying bloat by skroops · · Score: 1

      yeah because no one in a position of power has ever made a bad decision...

    35. Re:Incredible horrifying bloat by EvanED · · Score: 2, Insightful

      add-ons, by definition, are not part of the application.

      No, but the code that loads and runs the add-on is.

    36. Re:Incredible horrifying bloat by ketilwaa · · Score: 1

      It's not a third party addon, it's a feature you can enable or disable that is an integrated part of Tomboy.

    37. Re:Incredible horrifying bloat by ketilwaa · · Score: 1

      I made a slight mistake in my spelling, so I can understand some of the confusion. Gnote calls them "add-ins". My Norwegian translation of Tomboy calls them "Tillegg", which is the same word used to describe Firefox addons/extension. They're not extensions like you're used to in Firefox, but features you can turn off or on, that comes with the app.

    38. Re:Incredible horrifying bloat by phantomfive · · Score: 1

      I know that writing code is the easier part of software development.

      Just for curiosity's sake, what exactly do you consider to be the hard part of software development? Testing? Debugging? Because writing in C# tends to make the debugging easier as well......

      --
      Qxe4
    39. Re:Incredible horrifying bloat by Anonymous Coward · · Score: 0

      I have a compiled version of Tomboy and it only comes out to around 5-6 megs.

      A 20 minute download for a note-taking app?

      Omg, that is 0.0006% of my hard drive.

    40. Re:Incredible horrifying bloat by shutdown+-p+now · · Score: 1

      You see, Linux/Unix/BSD don't need Mono! What can you achieve using Mono which you wouldn't achieve with Perl, Python, C++ or Java? Name one, please, only one.

      Conversely, what can you achieve using Java that you wouldn't achieve with Mono? Or, for that matter, what can you achieve using insert-any-programming-language-here that you wouldn't achieve with Common Lisp?

      It's all a matter of perspective and starting point.

    41. Re:Incredible horrifying bloat by shutdown+-p+now · · Score: 1

      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.

      I'm not sure what wrong there is with C# language design, given that it has almost complete feature parity with C: unlike Java, it supports stack-allocated value types, including unions; pointers with pointer arithmetic, which enables unchecked arrays; and even alloca. Granted, you usually don't use any of those when "writing code blazingly fast", but there's always an option.

      Anyway, I hope you're at least consistent in your views, and also don't use any applications written in shell scripts, Perl, Python, Ruby, Scheme, Tcl...

    42. Re:Incredible horrifying bloat by Anonymous Coward · · Score: 0

      Honestly, there was a time where perl, gcc, binutils, glibc, net-tools, what is now coreutils, and the automake/conf toolchain were all you needed to compile and install a system. If I remember correct, circa 2000, all that took up at least a gig in source form. Flash forward to today, and I think I'm installing 3-4 gigs worth of source, and ~another 3-4 gigs in object files to come out with a usable system. Not only that, but going back more than a year for libraries/system utilities, etc and they're IMPOSSIBLE to use, because they don't support either a newer, or older kernel.

      What happened to API stability? What happened to a userspace that you could almost remember off the top of your head? What happened to being able to compile your own system without spending a week tracking down some minor version update to some package that you need in order to compile your FRICKING CORE system?

      *a linux n00b as of the late 90's, now a salty old geezer*

    43. Re:Incredible horrifying bloat by Anonymous Coward · · Score: 0

      Maybe not in Debian because it excludes them but a whole host of other default gnome apps do share it.

      OK, but we're talking about Debian. I, for one, have no apps that use Mono. If I wanted tomboy the requirements are not just the tomboy code itself, but also all the packages that will have to be installed specifically for this one application. Which means about 50 megs. It's not an unfair characterization. Tomboy equals 50 megs to install, no tomboy equals 50 megs available for other uses. 50 megs is simply outrageously bloated for a note-taking app. Even the 5 megs for just tomboy alone is outrageously bloated, but that's a whole separate gripe.

    44. Re:Incredible horrifying bloat by Anonymous Coward · · Score: 0

      dude, you're quibbling over technicalities. face it, gnote is a "good enough" C++ port of the C# version. minor variation is inevitible but does not invalidate that core fact. the lack of mono (you must admit in many people's eyes, if not your own) appears to more than make up for any lag in gnote's feature set. Guessing that the core addins were ported first and newer/less interesting ones have been put off until later.

    45. Re:Incredible horrifying bloat by neiras · · Score: 1

      If we are talking about replacing tomboy with gnote, we need to have some data migration that is more automatic that 'open terminal, cp .tomboy .gnote'.

      Your wish is granted: See the Gnote developer's blog.

      Keep in mind that gnote is very, very young. It's come a long way in a short time. I don't think we have too long to wait before it hits feature parity with Tomboy.

    46. Re:Incredible horrifying bloat by Dragonslicer · · Score: 1

      You see, Linux/Unix/BSD don't need Mono! What can you achieve using Mono which you wouldn't achieve with Perl, Python, C++ or Java?

      Wouldn't, or couldn't? They're all Turing-complete languages. If you mean couldn't, then by your argument, Linux doesn't need Perl, Python, C++, or Java, either, because it has assembly. If you meant what you wouldn't do, I can think of plenty of things that I would much rather use C#/.Net for than Perl or Python (Java is a bit harder of course, since Java and C# are such closely-related languages). I can also think of several things where I'd rather use Perl or C instead of C# or Java. Every language has its strengths and weaknesses, plus the fact that different programmers have different preferences.

    47. Re:Incredible horrifying bloat by Dragonslicer · · Score: 1

      Or, for that matter, what can you achieve using insert-any-programming-language-here that you wouldn't achieve with Common Lisp?

      Finishing a program without having horrible nightmares about being attacked by hordes of closing parentheses?

    48. Re:Incredible horrifying bloat by Randle_Revar · · Score: 1

      >or do other parts of Gnome depend upon Mono now?

      It depends on what you mean by "other parts of Gnome". There are a number of other Gnome apps written in C#, including Banshee (music player) and G-Spot (photo management). But none of those apps are "officially" part of Gnome (I don't remember what terminology they use). Having Mono one step removed like that is something that seems unlikely to change anytime soon.

    49. Re:Incredible horrifying bloat by Dragonslicer · · Score: 1

      Just for curiosity's sake, what exactly do you consider to be the hard part of software development? Testing? Debugging? Because writing in C# tends to make the debugging easier as well......

      For me, it would be reading and maintaining someone else's code. Some languages may encourage more readable code than others, but a bad programmer will write terrible code no matter what language you give them.

    50. Re:Incredible horrifying bloat by sjames · · Score: 2, Insightful

      When dependencies are included, the picture gets a little muddy, but in this case, it's reasonable to do so. Essentially, since a default desktop install will pull in all of mono ONLY to satisfy tomboy's dependencies, mono's size needs to be added to the effective weight.

      Things like glibc are not part of it's weight because it is used by a great many things by default and practically nothing can be installed without it.. Instead, glibc's weight is added to the weight of the minimum install.

      Put another way, the weights of dependencies are added to the topmost element required for a credible install of that feature. Mono's weight isn't added to Gnome since an install of Gnome without Tomboy is perfectly credible. In turn, the weight of Gnome isn't added to that of X because X without Gnome is also credible. Instead, the weight of the smallest useful window manager should be added to X since X with no window manager at all, while possible and even desirable for a few niche cases, isn't really credible for a typical use.

      Questions of exactly what is 'credible' is where the mud comes in.

    51. Re:Incredible horrifying bloat by Randle_Revar · · Score: 1

      >My personal windmills are applications like HAL, D-BUS, any gnome-*-daemon, any {Policy,Device,Console}Kit

      Actually, all of those are very useful, with the possible exception of some of the gnome daemons (and some of those are going away, as soon as Gnome finishes dropping Corba). HAL is useful, but of course has problems, which is why we are now in a smooth transition from HAL to DeviceKit-*. PolicyKit is an excellent way to handle permissions in a GUI - far better than GtkSudo, etc. ConsoleKit helps with a number of session-related issues, particularly allowing fast user switching. D-Bus is needed because a modern desktop really needs some good IPC outside the basic shared memory, pipes, etc. D-Bus does a good job of providing this.

    52. Re:Incredible horrifying bloat by Randle_Revar · · Score: 1

      Err, F-Spot. The name is just almost naughty, not actually naughty.

    53. Re:Incredible horrifying bloat by shutdown+-p+now · · Score: 1

      Well, you can always define reader macros in CL so the syntax can be absolutely anything you want. Heck, you could even use indentation to define implicit parentheses.

    54. Re:Incredible horrifying bloat by jgrahn · · Score: 1

      You mean other than the fact that the statement is bullshit? I have a compiled version of Tomboy and it only comes out to around 5-6 megs.

      You're probably right, but 5--6 megs is a lot, too. On my system, the only binary larger than that is emacs (at 6.7 megs). (Oh, I know there are lots of other things which need disk space, but I can't be bothered to find out how to sort my dpkgs by install size.)

      Not that any of this really concerns me. I don't let Gnome come anywhere near my three or four Debian systems. Nor KDE for that matter.

    55. Re:Incredible horrifying bloat by jmorris42 · · Score: 1

      > ..it only comes out to around 5-6 megs.

      You do know that attitude is what is killing us. It is an APPLET. Only 5-6megs.... Of course it could be much worse. Have a look at libgweather. It lets the clock applet show the local weather. On Fedora 10 it weighs in at 80MB, mostly a bunch of XML horror that nobody thought to gzip.

      But with Tomboy/Mono it is the resident set that should be the dealbreaker. Applets should not consume more RAM at idle than an entire POSIX environment would need to happily run in a generation ago.

      --
      Democrat delenda est
    56. Re:Incredible horrifying bloat by StrawberryFrog · · Score: 3, Insightful

      We can't expect small, lean applications written in C# because of the language's design.

      Why not? What design feature stops this?

      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.

      Indeed, you need readable, maintainable, performant code. Which is why I use C#. You were expecting perl maybe?

      --

      My Karma: ran over your Dogma
      StrawberryFrog

    57. Re:Incredible horrifying bloat by StrawberryFrog · · Score: 1

      "C# "application" .. calling something written in a scripting language anything other than a script"

      What exactly is your criteria for calling a language a "scripting" language? I am curious, since if you consider C# a scripting language (and Java too, I suppose, they have similar architectures) you must have a very odd definition of scripting language. Or you're just trolling.

      --

      My Karma: ran over your Dogma
      StrawberryFrog

    58. Re:Incredible horrifying bloat by Nevyn · · Score: 1

      PolicyKit is an excellent way to handle permissions in a GUI - far better than GtkSudo, etc.

      Or not. Try doing an install in PackageKit, and then removing the same thing ... you get asked to authenticate twice (retarded), and if the removal is allowed there's no way to deny that same user from removing glibc as well (double plus retarded). Now it's possible this is all PackageKit is PolicyKit is awesome, but AFAICT that's not true and the usual answer seems to be along the lines of "PolicyKit is designed to let a normal local user change the time from the gnome-panel, and works as long as your problem domain is of a similar level of complexity.".

      Also ... please don't think about what happens when you have GUI applications that have arbitrary privilages, ptrace() doesn't exist etc. (actually the std. PolicyKit response is to disallow ptrace()/core/etc. on startup ... and pretend that's clever, and actually works).

      --
      ustr: Managed string API with ave. 44% overhead over strdup(), for 0-20B
    59. Re:Incredible horrifying bloat by jmorris42 · · Score: 3, Interesting

      > Actually, all of those are very useful,....

      No, they might be useful someday. Today they are all semi-stable and almost totally undocumented black boxes that upend forty years of UNIX/POSIX tradition yet were pushed into production in this insane quest to be a better Windows than Windows and thus somehow bring about the Year of Linux on the Desktop.

      So while all of the old understood ways of configuring a system have been tossed into the trash, the new replacements aren't ready for prime time. By ready I mean 'just works' at least 99% of the time and has clear documentation to permit a skilled UNIX admin to fix that last 1%.

      Example: The hpt_37x driver has been broken[1] (massive data corruption) in Fedora's kernels since at least F8 and probably earlier. With a few tweaks the open source driver at Highpoint's website can be built and works. Your mission, get F11 to use it. I finally this did it this morning by editing /etc/sysconfig/mkinitrd and having it force the driver to load in the initrd phase before the *Kit bullcrap gets a chance to start.

      [1] It isn't Fedora's fault. Kernel mailing list traffic shows a problem that has been fixed, regressed and fixed yet again, rinse and repeat a time or two. From what I can tell 2.6.30 may finally have it fixed but F11 shipped with 2.6.29.

      --
      Democrat delenda est
    60. Re:Incredible horrifying bloat by kelnos · · Score: 1

      Well, that's much better. 50MB for a note-taking app is absolutely ludicrous. 5-6MB for a note-taking app is only garden-variety ridiculous.

      --
      Xfce: Lighter than some, heavier than others. Just right.
    61. Re:Incredible horrifying bloat by kelnos · · Score: 1

      A technology doesn't become invalid just because you can achieve all of the same goals by using a different technology. People like C#. There's a market for mono. Unless you've written apps in all the languages you mention (as well as C#), you really can't say which is "better" -- and even that is a subjective opinion.

      Having said that, I dislike C# and Mono, and wish it wasn't necessary. Maybe that's just because C# and .NET come from Microsoft, but... that's where my opinion stands. I don't trust them.

      --
      Xfce: Lighter than some, heavier than others. Just right.
    62. Re:Incredible horrifying bloat by Draek · · Score: 1

      You see, Linux/Unix/BSD don't need Mono! What can you achieve using Mono which you wouldn't achieve with Perl, Python, C++ or Java?

      Same thing you can achieve with Python that you can't with Perl: absolutely nothing. Turing completeness and all that. But I'm sure you understand the idiocy of "one language to rule them all"-style arguments, seeing as you mentioned more than one yourself so why the hatred on C# in particular?

      Ohhh I get it, it's because it's from *Microsoft*! save your FUD for when you've actually tried it, boy, because if you think C# and the .NET enviroment bring nothing new to the table its clear you haven't done so yet.

      --
      No problem is insoluble in all conceivable circumstances.
    63. Re:Incredible horrifying bloat by Bazer · · Score: 1

      It's not misleading when that environment is not a standard (ditto for applications which depend on it). If I'd write an applet that required you to install Haskell then I guess you wouldn't count the size of ghc either?

      For the heck of it, here's a test case for a default install of Fedora 11. Removing the "mono-core" package yields:

      Removing:
      mono-core
      Removing for dependencies:
      gnome-desktop-sharp
      gnome-sharp
      gtk-sharp2
      mono-addins
      mono-data
      mono-data-sqlite
      mono-extras
      mono-web
      mono-winforms
      monodoc
      ndesk-dbus
      ndesk-dbus-glib
      tomboy

      What are those "default" applications you speak of?

    64. Re:Incredible horrifying bloat by Anonymous Coward · · Score: 0
      See what Rahul said in his post in this very discussion. I'll quote it here if you don't want to click the link:

      I am Rahul Sundaram, maintainer of Gnote in Fedora that you are quoting from. We did manage to include Gnote as the default replacing Tomboy in Fedora 12. For one, GNOME system monitor already is using gtkmm and boost has been split in Fedora 12 to be more granular.

    65. Re:Incredible horrifying bloat by sgt+scrub · · Score: 1

      yes. i call java a scripting language too.

      --
      Having to work for a living is the root of all evil.
    66. Re:Incredible horrifying bloat by sgt+scrub · · Score: 1

      C# isn't a scripting language. You clearly don't know what a scripting language is to make such a laughable statement.

      Anything that is not compiled before being distributed is a scripting language in my book. So, yes, I guess I don't know because I choose not to be that specific.

      Because no C/C++ application is accompanied by extra baggage? I guess I must be dreaming every time I download one of them and have to download 5-10+ megs of dependencies when I apt-get one.

      Agreed. C/C++ applications that require additional libraries to run are annoying. However, having a JIT to keep up to date AND additional libraries is even more so.

      Note: I dislike Java just the same. You .NET lover/hater's can have your war. I'm happy to be one of those that happens (dis)like everything in one way or another.

      --
      Having to work for a living is the root of all evil.
    67. Re:Incredible horrifying bloat by Anonymous Coward · · Score: 0

      Cool. I've started looking at porting Gnome Do to JRuby.

      Who needs Mono?

    68. Re:Incredible horrifying bloat by diegocgteleline.es · · Score: 1

      bash-static, but then the whole purpose of that package is to build everything static :)

    69. Re:Incredible horrifying bloat by jrumney · · Score: 1

      I have a compiled version of Tomboy and it only comes out to around 5-6 megs.

      Dude, I have a compiled version of Emacs that comes out to 3.5Mb. So remind me again why a note taking application should take up so much space, plus depend on 45Mb worth of Mono framework.

    70. Re:Incredible horrifying bloat by Tetsujin · · Score: 1

      > Actually, all of those are very useful,....

      No, they might be useful someday. Today they are all semi-stable and almost totally undocumented black boxes that upend forty years of UNIX/POSIX tradition yet were pushed into production in this insane quest to be a better Windows than Windows and thus somehow bring about the Year of Linux on the Desktop.

      So while all of the old understood ways of configuring a system have been tossed into the trash, the new replacements aren't ready for prime time. By ready I mean 'just works' at least 99% of the time and has clear documentation to permit a skilled UNIX admin to fix that last 1%.

      My perspective:
      I appreciate the history and tradition of Unix/Posix but I don't believe any of it is beyond the need for improvement.

      For instance, what's the "old and understood" method for writing an application to which another process can connect at runtime and send commands, or receive notifications? SYSV IPC? Binding to some random port number, hoping nobody else is using it, and waiting for connections? Putting a named pipe somewhere on the filesystem and... (you'll have to forgive me, here - I haven't learned quite enough to know all the details of how to implement a thread-safe application object interface via named pipes...)

      Or what's the "old and understood" method for an application to receive notification when the disk is full? Or when a USB device is inserted?

      I'm with you to a point: that the changes in how things are done in the last several years have been a bit baffling and hard to keep up with at times. But I feel like in general it's been good stuff. Each time the system gets a bit more coherent, a little better suited to what I want it to do...

      --
      Bow-ties are cool.
    71. Re:Incredible horrifying bloat by suffix+tree+monkey · · Score: 3, Insightful

      What design feature stops that?

      Code size: Well, C# is a pretty verbose language, much like Java. Usually you need to write a lot of "wrapping-paper" code to do what you need the program to do. That helps when you prefer a lot of subprojects that should behave alike, but that's not what we like to do in UNIX (We like to stitch our system together with small applications that do their tasks and only their tasks well.).

      Application speed: Well, as far as I had the privilege of testing Mono/C#, it may perform as well as C in number-crunching, but its garbage collector slows things down sometimes (which is a design decision, and you can write code faster, I know, I know) and the I/O is also pretty slow compared to C/C++ (this I measured myself). By the way, parsing files (UNIX always was a text-processing OS) is a PITA to write in C# (unless you're using XML, but that's not how we roll in UNIX-land, most of the time).

      Indeed, you need readable, maintainable, performant code. Which is why I use C#. You were expecting perl maybe?

      I prefer readable, well-thought-out code. You get performance for free if you thought about it at the drawing board. Maintainability is hardly measurable. (I don't consider code bad if you need a "suffix tree monkey" to maintain it, cause the "code monkeys" are unable to.)

      PS: I'm sorry I haven't brought any verifiable data to the table, but I'm currently far too into theory to care about any of those :o) Everything above is my experience, YMMV.

    72. Re:Incredible horrifying bloat by suffix+tree+monkey · · Score: 1

      Just for curiosity's sake, what exactly do you consider to be the hard part of software development? Testing? Debugging? Because writing in C# tends to make the debugging easier as well......

      The hard part would be designing the software correctly, choosing the appropriate data structures and algorithms, calculating the estimated algorithm complexity, planning all the features and making sure the code is extensible in the future (if there are plans for that).

      For me, it's always paid out to spend as much time as possible thinking about the theoretical side. After that, you have a really good idea on what you want to do, and you don't have to stop and think about that code too much. But I admit, debugging and testing are the bothersome parts of software development - you can never eliminate them completely. Kudos to C# for trying to minimize time spent on those. It's a sad fact that a lot of coders think the design part can be skipped as well. (I'm not above those people, I used to code like that, too.)

    73. Re:Incredible horrifying bloat by Tubal-Cain · · Score: 1

      For comparison, on my system removing libc6 from Ubuntu would break 1288 packages.

    74. Re:Incredible horrifying bloat by suffix+tree+monkey · · Score: 1

      Or what's the "old and understood" method for an application to receive notification when the disk is full? Or when a USB device is inserted?

      I agree with the above sentence (and I completely agree with the GP, he nailed it on the head). The problem I see with modern distros (modern GNU/Linux) is that many of those features that somebody "needs" are being hacked into the system without really thinking about the big picture. Basically, we're just hacking extra stuff into GNU/Linux that somebody wants to have now, because she saw it in a different OS and it seemed nice.

      Do you know which OS tried to please everyone with extra featurettes that were copied from other systems, and layer upon layer of abstraction and backwards compatibility? It ended with a particular version of that OS which everyone hated, and I don't want Linux of 2012 to be the equivalent of that version.

    75. Re:Incredible horrifying bloat by bonefry · · Score: 1

      Gnotes is just a fork, line by line, done with the sole purpose of replacing Tomboy, worked on by one individual that's on some kind of a holly quest.
      Not to mention that Gnote's license is GPL3, and porting features back in Tomboy (assuming there will ever be features worth porting) is currently not possible.

      Tomboy, although it's "just a post-it" application, it does have usefulness and innovation in it.
      Of course the Tomboy devs are annoyed. I would be too.

    76. Re:Incredible horrifying bloat by StrawberryFrog · · Score: 1

      You need to find another word, since that word "scripting", it does not mean what you think it means.

      --

      My Karma: ran over your Dogma
      StrawberryFrog

    77. Re:Incredible horrifying bloat by walshy007 · · Score: 1

      You see, Linux/Unix/BSD don't need Mono! What can you achieve using Mono which you wouldn't achieve with Perl, Python, C++ or Java? Name one, please, only one.

      Interoperability with uni courses that demand you program in it. I do not want to have to have windows installed just to program uni assignments, thankyou

    78. Re:Incredible horrifying bloat by walshy007 · · Score: 1

      Anything that is not compiled before being distributed is a scripting language in my book. So, yes, I guess I don't know because I choose not to be that specific.

      well then by your own definition you wouldn't consider either c# or java as a scripting language then... hint, they are compiled, they run on a virtual machine though.

      If I were to write a program for the snes using a 65816 assembler, would you then consider it a 'script' when I ran it on zsnes or the like? I doubt it. That a native hardware implementation of the vm c# apps run on doesn't exist means nothing. (oh and there is native hardware for java, any arm processor with jazelle)

    79. Re:Incredible horrifying bloat by StrawberryFrog · · Score: 1

      Code size: Well, C# is a pretty verbose language, much like Java. Usually you need to write a lot of "wrapping-paper" code to do what you need the program to do. That helps when you prefer a lot of subprojects that should behave alike, but that's not what we like to do in UNIX (We like to stitch our system together with small applications that do their tasks and only their tasks well.).

      It's true that both C# and Java require a bit of Wrapper code before you get started, e.g.


      namespace MyProgram.Foo
      {
            public class Fred
            {
                public void SomeMethod()
                { // actually get started here

      The reason for that is for organising large bodies of code. Which is exactly why C++ has namespaces too. I'm not sure why you think this is not "Unixy" - two of those systems, C++ and Java, come from UNIX land. Suggesting that nobody ever writes large applications on UNIX is absurd, applications of all sizes have their uses on any operating system. I'm not talking about OS utilities like "ls" and "more" here. Accounting, stock trading or CRM packages aren't constructed out of small utils and command-line pipes.

      Your original post was about "small, lean" applications, and I think you're mixing up the verbosity of the source code and the size of the resulting executable, which are two very different things. C# and Java optimise the source for readability.

      The code inside a C# method can be terse if you choose to write it that way. Here's a line that I wrote recently:
      viewModel.AddList(groupLinks.Select(gl => new GroupFilterSelection(gl)));

      Which constructs a list of objects and adds them to another list.

      --

      My Karma: ran over your Dogma
      StrawberryFrog

    80. Re:Incredible horrifying bloat by Anonymous Coward · · Score: 0

      He does look biased against Mono, but how does this make his complaints less valid? The points stay:
          - Both Tomboy and Gnote are functionally equivalent
          - Gnote is faster, consumes less disk and less memory

    81. Re:Incredible horrifying bloat by Ilgaz · · Score: 1

      If it is just 50 MB , .NET clone of Linux really lacks some huge functionality.

      As I monkey around with 10-15 MB sized Windows virtual machine these days, I can say the real (yea Icaza, real) .NET framework weights around 1-2 GB when compiled behind users back after install.

      It was going to be way more but some sane people from MS finally figured they are becoming the joke of the decade (bitching about Java size) and slimmed down in 3.5 SP1 release.

      Also as I run the original thing on real Windows, I notice you can't just install the latest and be done with it like 99% of Java apps. You should have 1.x, 2.x, 3.x for full functionality of your installed apps.

      This thing was designed with the idea of 'killing' java. We see the results. Also, there is no Microsoft.NET for OS X, an OS which has no claim to be ''free'' as in everything. They rely on Icaza guy to ship half ass clone of Mono and expect OS X users who expects the best these days to buy it... They don't. OS X user/developer can't be bothered with a clone of a clone. Perhaps they will send some paypal money to a Icaza friend and he will ship something good requires Mono for some unexplainable reason? Well, it is real hard to race with native, Objective C++ stuff and real C/POSIX stuff on OS X.

    82. Re:Incredible horrifying bloat by Just+Some+Guy · · Score: 1

      yes. i call java a scripting language too.

      And I say a coffee cup is a zebra, and look disdainfully at people for their failure to understand my non-standard terms.

      --
      Dewey, what part of this looks like authorities should be involved?
    83. Re:Incredible horrifying bloat by sgt+scrub · · Score: 1

      I bought my zebra here.

      --
      Having to work for a living is the root of all evil.
    84. Re:Incredible horrifying bloat by badkarmadayaccount · · Score: 1

      Don't named pipes work wonderfully with message passing OO languages?

      --
      I know tobacco is bad for you, so I smoke weed with crack.
    85. Re:Incredible horrifying bloat by Xabraxas · · Score: 1

      What happened to a userspace that you could almost remember off the top of your head?

      People decided they wanted to do more with their Linux Desktop than just play nethack.

      What happened to being able to compile your own system without spending a week tracking down some minor version update to some package that you need in order to compile your FRICKING CORE system?

      Like what?

      --
      Time makes more converts than reason
    86. Re:Incredible horrifying bloat by Anonymous Coward · · Score: 0

      It may be reasonable to include it, but it is dishonest and misleading if you do not differentiate how much is the app and how much is the dependencies.

  6. Re:Yessss by Aphoxema · · Score: 1

    So, what's so good about mono?

    --
    "Most people, I think, don't even know what a rootkit is, so why should they care about it?"
  7. Looks more like Sid by El_Muerte_TDS · · Score: 3, Informative

    The commit was done on Debian unstable, which is Sid, not Squeeze.

    1. Re:Looks more like Sid by Anonymous Coward · · Score: 0

      Sid will become squeeze when squeeze is released. The commit was made to sid with the intent of having it be a part of the final squeeze release.

      It's like saying "The next Firefox release will have feature X", and you replying with "That feature is in the beta, not the final release."

    2. Re:Looks more like Sid by dlgeek · · Score: 2, Informative

      Not quite. Sid is always sid. Squeeze becomes stable when it's released. Packages automatically move from unstable (always sid) to testing (currently squeeze) when they have no RC bugs for 10 days and all their dependencies can move together. Eventually, this is frozen and all moves happen by hand, as the release is prepared. This change will propagate to squeeze soonish though, assuming there are no bugs.

  8. What the F... by sydneyfong · · Score: 5, Informative

    Am I missing something?

    I've been using Debian for ..... 8+ years, since 2001, and I've NEVER heard anything about "GNOME" being in the "default" install. Anything resembling a "default" install would be the the Debian base system, which includes things like basic system files, core-utils, bash, pam, etc. Anything else is installed explicitly by the user (yes, installers make it easier, but still you need to choose the option). There are thousands of Debian desktop users who have no GNOME installed, and are either using KDE, or some other desktop environment.

    Besides, isn't "tomboy" already included in the GNOME of Debian Lenny (the current stable release)? At least when I did an "apt-get install gnome" yesterday (source list pointing to lenny), it installed tomboy for me, together with the EVIL EVIL mono etc. And Debian has included mono as part of its repository for years. If it had licensing/patent concerns, there wouldn't be any difference whether it was in the "default GNOME" installation or not.

    Argh.

    --
    Don't quote me on this.
    1. 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.
    2. Re:What the F... by Theolojin · · Score: 1

      Am I missing something?

      I've been using Debian for ..... 8+ years, since 2001, and I've NEVER heard anything about "GNOME" being in the "default" install. Anything resembling a "default" install would be the the Debian base system, which includes things like basic system files, core-utils, bash, pam, etc.

      If one installs, via tasksel, the "desktop" environment, GNOME is installed by default. One can certainly install another window manager/desktop environment, but unless one specifies another wm/de, one gets GNOME. From the Debian wiki: "You could simply mark the Desktop environment option. It will install the packages for Gnome and some packages that are considered "standard" for a Debian desktop." (http://wiki.debian.org/tasksel) It is in this sense that GNOME is in the "default" install.

      --
      Life is short; think quickly.
    3. Re:What the F... by je+ne+sais+quoi · · Score: 1

      Incidentally, I've been using debian for about five years now and this behavior the last year or so to increase the number of packages included in "gnome" or "kde" meta-packages is a little annoying. The reason is that I might want gnome or kde, but I don't want all a full-blown desktop environment because it's bloated and has a whole bunch of stuff I don't need. I don't even know what tomboy or mono is, let alone use them, why would I want to install them by default? I wish they'd differentiate between a package that just installs gnome and then have another meta-package that includes all this other stuff that is no doubt helpful for some people, but not wanted in my case.

      As it is, with a new install I have to install a default, bare-bones installation and then install everything else by hand. So for kde, I install kde-base, kde-libs, kde-multimedia, etc. It's not that it's impossible to deal with this way, but for a user like me, when I think of "gnome" I think of gnome itself and not gnome + tomboy + mono + lots of other apps and utilities, etc. but I guess I'm in the minority.

      --
      Gentlemen! You can't fight in here, this is the war room!
    4. Re:What the F... by recoiledsnake · · Score: 1

      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.

      Gnote is not just a non-Mono replacement of Tomboy, it's a line by line ripoff of Tomboy's C# code to C++ and GUI design. See http://robertmh.wordpress.com/2009/06/12/mono-in-the-default-install/ for screenshots. And the developers of Tomboy are not happy.

      Our stance on Gnote is that it is counterproductive to maintain identical software in two languages. It will be harmful to the community, especially as these two apps inevitably diverge. It will result in duplication of effort, duplication of bugs, and a lot of wasted time for those who are trying to add value to the user experience. Tomboy is not going away, and it will continue to be developed on the extremely productive Mono/GTK# language platform. Anyone thinking about distributing Gnote should consider the impact on users and their data. When we develop, we should always be asking ourselves, "is this adding value for our users?"

      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.

      --
      This space for rent.
    5. Re:What the F... by christurkel · · Score: 1

      I think the submitter default desktop install. During the install you can have a "desktop environment", which will be Gnome with TomBoy.

      --

      CDE open sourced! https://sourceforge.net/projects/cdesktopenv/
    6. Re:What the F... by blind+biker · · Score: 1

      There are thousands of Debian desktop users who have no GNOME installed

      I would wager that there are millions - if you count the Debian derivatives, like Xubuntu, Kubuntu, Xandros, Knoppix.... there must be at least a couple million non-Gnome Debian users.

      --
      "The agriculture ministry is not in charge of Gundam" - Japanese ministry official.
    7. Re:What the F... by recoiledsnake · · Score: 1

      Edit: Tomboy is under LGPL.

      --
      This space for rent.
    8. Re:What the F... by bluefoxlucid · · Score: 1

      Hooray for dick stroking and comparing ego sizes!

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

    10. Re:What the F... by recoiledsnake · · Score: 3, 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.

      You are being too simplistic. Forks are more complicated than 'if Y is better than X then people will use Y and the world will be better'.

      Consider this, what's the sole motivation behind the development of Gnote? It is to remove the Mono dependency, that's all, there's nothing more to it. And the work is relatively easy because all the heavy lifting has already been done by the Tomboy developers.

      Say Gnote takes off and Tomboy dies, the motivation to improve Gnote is gone because the single goal of Gnote(i.e to kill Tomboy) has been achieved, and anyway, there is no more Tomboy to ripoff new ideas, code and GUI design from. Tomboy's developers are not happy with gnote now, so there's little chance they will jump ship to gnote.

      So there's more to this than survival of the fastest and slimmest.

      --
      This space for rent.
    11. Re:What the F... by Digana · · Score: 1

      It's default in the sense that if you stick in the recommended Gnome default desktop and just furiously click "next" during the installation, you'll get Gnome and Tomboy.

    12. Re:What the F... by Just+Some+Guy · · Score: 1

      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.

      Not in FOSS, there's not. I mean, it's good to be nice to the original developer, but if they do something you don't like, there's not reason not to do things your own way.

      --
      Dewey, what part of this looks like authorities should be involved?
    13. Re:What the F... by Anonymous Coward · · Score: 0

      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.

      Except that professional courtesy and respect go out the window when the developer (Joss) has never shown any of the same to the rest of the community, and so has widely gotten himself a public reputation as a complete dickhead. At that point people start going to significant trouble to code around him.

    14. Re:What the F... by Anonymous Coward · · Score: 0

      Professional courtesy and respecting a developer's wishes? Fuck that! It's my right to download music. Developers should make money by selling tshirts at concerts (which should also be free).

    15. Re:What the F... by binarylarry · · Score: 1

      Because nobody fucking wants Mono on their system!

      --
      Mod me down, my New Earth Global Warmingist friends!
    16. Re:What the F... by Anonymous Coward · · Score: 0

      The âoegnomeâ metapackage is here for the full-fledged desktop, sticked with every functionality that could be useful for a reasonable number of people.

      If you want a lighter installation, just select by hand the âoegnome-coreâ or âoegnome-desktop-environmentâ package.

    17. Re:What the F... by recoiledsnake · · Score: 1

      Speak for yourself. There are users who either don't care or don't mind using a application that has Mono as a dependency.

      --
      This space for rent.
    18. Re:What the F... by recoiledsnake · · Score: 1

      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.

      Except that professional courtesy and respect go out the window when the developer (Joss) has never shown any of the same to the rest of the community, and so has widely gotten himself a public reputation as a complete dickhead. At that point people start going to significant trouble to code around him.

      Citation needed.

      --
      This space for rent.
    19. Re:What the F... by je+ne+sais+quoi · · Score: 1

      Nice. Thanks for the update, I hadn't looked for awhile and having these core packages will be useful next time I install on a new machine.

      --
      Gentlemen! You can't fight in here, this is the war room!
    20. Re:What the F... by Anonymous Coward · · Score: 0

      I guess they're the same users who wouldn't care or wouldn't mind switching to Windows after that application can no longer be found in Linux distributions because of legal threats from Microsoft.

    21. Re:What the F... by shutdown+-p+now · · Score: 3, Insightful

      Consider this, what's the sole motivation behind the development of Gnote? It is to remove the Mono dependency, that's all, there's nothing more to it.

      Well, and what is wrong with that? If there is a demand to remove Mono dependency (and apparently there is), then the fork serves a useful purpose.

    22. Re:What the F... by Randle_Revar · · Score: 1

      Tomboy has been a "recommends" until now, I believe. Which means it gets installed unless you exclude it manually or set APT to not automatically install recommends.

    23. Re:What the F... by lordlod · · Score: 1

      Say Gnote takes off and Tomboy dies, the motivation to improve Gnote is gone because the single goal of Gnote(i.e to kill Tomboy) has been achieved, and anyway, there is no more Tomboy to ripoff new ideas, code and GUI design from. Tomboy's developers are not happy with gnote now, so there's little chance they will jump ship to gnote.

      I think the goal of Gnote is to have a good note application like Tomboy that doesn't require Mono. Any killing of Tomboy is just a side effect.

      If Tomboy died the core developers probably wouldn't switch but many of the minor contributors will and all the future contributors will including the new eyes that see a better way to structure something or a really nice new feature. Gnote will continue to grow.

    24. Re:What the F... by Anonymous Coward · · Score: 0

      > Consider this, what's the sole motivation behind the development of Gnote? It is to remove the Mono dependency that's all, there's nothing more to it.

      False! Where did you get this from?

  9. 6 MB by Anonymous Coward · · Score: 1, Informative

    It's actually 6 MB for Tomboy itself. The 50 MB figure must include Mono, I guess.

  10. An interesting read on the subject by Dotren · · Score: 3, Insightful

    Not really being much of a Linux person myself yet, I was curious about the negative feelings I've read about for Mono, ranging from general dislike to outright hate, as I've had several people tell me that Mono is actually really cool and easy to use if you're used to doing .Net programing in general. Malevolentjelly posted this link a few days back in the Silverlight 3 post and I found it very informative:

    http://www2.apebox.org/wordpress/rants/124/

    1. Re:An interesting read on the subject by Freetardo+Jones · · Score: 3, Insightful

      C# is very good language, though not perfect, which builds on many of the good innovations of Java while eliminating many of the issues that I've always had with Java. The reason why there are so many negative feelings is because this is a Microsoft technology and nothing more. If Microsoft had originated the specification of ANSI C exactly as it is today, for example, you would hear constantly all the same outcries about how crappy it was, etc etc.

    2. Re:An interesting read on the subject by slashbart · · Score: 2, Insightful
      reetardo Jones doesn't get the reason for the negative feelings about mono at all. They originated because of the way mono is conceived to lure Linux developers into using software whose api is completely controlled by Microsoft but without its blessing. Once too many Linux packages depend on mono, I'm sure we'll get some patent/copyright saber-rattling from Microsoft.

      Then there's the technical aspect that mono will always be running behing the microsoft C#/CLI version, and so your Linux mono application will generally not even run on Windows, or if it's running will be unappealing because it feels old to the MS user. Windows platform cli application almost never run on Linux, so that's not an advantage either.

      So all in all we have here a technology that is offering nothing much, for a great future risk. No wonder we avoid it like Pfeiffers disease (or mononucleosis).

      If one wants to develop great crossplatform apps, use Qt, it has all and more of the advantages, and none of the risks.

    3. Re:An interesting read on the subject by Freetardo+Jones · · Score: 3, Informative

      They originated because of the way mono is conceived to lure Linux developers into using software whose api is completely controlled by Microsoft but without its blessing.

      Yeah, so much of a lack of a blessing that it's provided the Mono developers with specifications for .NET/C#/Silverlight and its engineers have directly collaborated with the Mono developers. I'm pretty sure if you weren't giving your blessing that you wouldn't allow your engineers to collaborate with the project.

      Once too many Linux packages depend on mono, I'm sure we'll get some patent/copyright saber-rattling from Microsoft.

      So you claim, but we've been hearing that for 5 years now and the sky hasn't fallen yet Chicken Little.

      Then there's the technical aspect that mono will always be running behing the microsoft C#/CLI version, and so your Linux mono application will generally not even run on Windows or if it's running will be unappealing because it feels old to the MS user.

      This is bullshit. Every app I've written against Mono that doesn't use any of their extensions has run perfectly on .NET on Windows. Just so you know, Mono supports pretty much all of the important parts of .NET 3.5 so I don't know where you are pulling this shit from.

    4. 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)
    5. Re:An interesting read on the subject by Anonymous Coward · · Score: 0

      Of the static VM languages, Mono C# is favored by the C++ type of programmer. C# includes all kinds of things that hide what is really going on, but make the code more less wordsy.

      Java is favored by the C crowd since like C you can look at any piece of code and know exactly what it is doing; there might be some #define but after a simple substitution you get the actual code. There's no automatic type conversions, no methods being defined in multiple files, no overloading, no 'copy constructors' or any other magic.

      So basically you have a normal C vs C++ type schism over mono in addition to it being 'tainted' by being based on Microsoft. A double-whammy. Plus the fact that it takes a 50mb runtime to make a program that does post-it notes and that it's barely faster than LuaJIT doesn't help...

    6. Re:An interesting read on the subject by Malc · · Score: 1

      Then there's the technical aspect that mono will always be running behing the microsoft C#/CLI version, and so your Linux mono application will generally not even run on Windows, or if it's running will be unappealing because it feels old to the MS user. Windows platform cli application almost never run on Linux, so that's not an advantage either.

      Surely it would be the other way around? Microsoft are extremely good at backwards compatibilty, and futhermore they haven't ditched the older versions of the .Net Framework any way, so something targetted for 1.0 or 1.1 will still run, even though they're working on newer versions. It's the Linux world where backwards compatibility is constantly being broken. As for appearance, the Mono team have chosen not to implement Windows.Forms (for obvious reasons), so that will be a bigger issue than running on an older version of the framework.

    7. Re:An interesting read on the subject by Anonymous Coward · · Score: 0
      • "Mono is not the result of any deals between Novell and Microsoft. " but it is explicitly affected by them. Novell bought Mono then MS bought Novell's good will.
      • Pushing Mono in the default risks making OIN waste a lot of money defending against MS in a case they can certainly win. As MS holds patents for this technology some of which are not covered by any of their promises not to sue. After OIN dies a terrible die for defending this Mono tantrum, all the other OIN-protected projects will be at risk. Great.
      • Still no way to get any Royalty-free license, regardles of what Jo claims.

      "GREAT APPS" none of which are really needed. Everybody who is used to good desktop photo software hates F-spot just as much as g-thumb. Some people like tomboy but they couldn't differentiate it from g-note. Rhythmbox is acclaimed the second best music libray player, just after Amarok (which regardles of the WE WANT GREAT APPS mantra, is not in the ubuntu default, odd?) Banshee is still, far , far, far ,fAR aways. For some reason Jo just forgets about the GREAT APPS mantra when he pushes Banshee out of a mythical package size argument! Of course, just dumping Mono altogether and replacing F-spot with gthumb and tomboy with gnote would boost freaking tens of megabytes, unlike the mere 6 MB that replacing Rhythmbox with Banshee would. What's worse are the attempts to smear against Rhythmbox development when it didn't stop: more info

    8. Re:An interesting read on the subject by slashbart · · Score: 1

      So you claim, but we've been hearing that for 5 years now and the sky hasn't fallen yet Chicken Little.

      That's because there has been rather little use of mono in the free software world. Once the Gnome core becomes mono or something similar, then we'll see.
      Fortunately there are quite a lot of developers in the Linux world that think like I do, so for now the risk is small.

    9. Re:An interesting read on the subject by Anonymous Coward · · Score: 0

      Once too many Linux packages depend on mono, I'm sure we'll get some patent/copyright saber-rattling from Microsoft.

      So you claim, but we've been hearing that for 5 years now and the sky hasn't fallen yet Chicken Little.

      Give it a bit of time! The Microsoft-Novell patent deal (i.e. Microsoft promises not to sue Novell's Linux customers for using Microsoft's precious technology for a limited number of years) runs out in November 2011, I'd wait and see.

    10. Re:An interesting read on the subject by nschubach · · Score: 1

      http://www.groklaw.net/article.php?story=20071023002351958

      The first hit is always free. Once Microsoft has you on their technology, then they start pulling in the reigns. A Linux developer using Microsoft standards is considered a battle won in their "holy war."

      --
      Every time I start to have faith in humanity, I ruin it by driving to work between 7 and 8 am.
    11. Re:An interesting read on the subject by Kz · · Score: 3, Insightful

      For me at least, the problem is not that it's an MS-originated tech; but the fact that it's an MS-controlled tech.

      A small counterpoint: XMLHttpRequest, the base call behind al things AJAX, is MS-originated; but it has evolved from that, and it's a widely complied de-facto standard. In fact, IE8 accepts the non-MS variant.

      Mono, OTOH, is a great reimplementation of .NET/C#; but is in most aspects following the obvious leader, which is MS. Just read some of Miguel's blogs. He's perennially awed of each microsoft improvement, and rushes to copy it. He does it brilliantly, and I wouldn't be surprised if he does it better than MS; but he still follows, not leads.

      Recently, thought, Mono has gained a few improvements over .NET, such as static compiling (compile to static machine code that can run without the VM), and SIMD optimizations (to transparently use SSEx, big performance improvements on some kind of media-heavy loads). Let's hope him and his team well, so that Mono could start to erode .NETs dominance on windows too.

      Personally, not holding my breath, and I don't want Mono on my machines.

      --
      -Kz-
    12. Re:An interesting read on the subject by _Sprocket_ · · Score: 1

      Yeah, so much of a lack of a blessing that it's provided the Mono developers with specifications for .NET/C#/Silverlight and its engineers have directly collaborated with the Mono developers. I'm pretty sure if you weren't giving your blessing that you wouldn't allow your engineers to collaborate with the project.

      Awesome... now all we need to do is clear up the little niggling license / patent thing.

      So you claim, but we've been hearing that for 5 years now and the sky hasn't fallen yet Chicken Little.

      I've never been mugged. That doesn't make me immune to mugging nor does it mean I shouldn't be wary of my environment.

    13. Re:An interesting read on the subject by gbjbaanb · · Score: 2, Insightful

      Fair enough, but there is 1 issue that I have with .NET and its the same issue I had with Java: lock-in.

      Remember the "100% pure Java" logos and disclaimers? The problem there is that they're telling you its ok to use Java, as long as you use Java too. You can do anything you want, as long as its written in Java. .NET is the same, though to be fair, the interop is better but I feel that is a legacy issue that MS will want to slowly use much less of, I see this already - if you write a GUI in .NET, WPF == .NET only, you'll find it difficult to do it using C++ only for example, and there is no code-behind in C++, only a .NET language. In other words, starting to write in .NET means to continue to write in .NET.

      With the native development tools, they all had a C interface to be compatibly with everything else - any library was designed to be used by anything you wanted, Python, Java, Perl all have bindings for C. But with .NET/Java, once you've written your library, its effectively only usable by other .NET/Java apps.

      I like interoperability. I like being able to reuse other people's hard work. I like free software.

      This also applies to server applications - if I want to run a web server, its fine - get mod_x going and I'm pretty much ready to go. If its a Java app, then suddenly I need to install tomcat or similar and get that whole application server framework running before I can run my little java app. I don't like this - all that overhead that doesn't need to be there, it offends my sensibilities as a professional programmer, as someone who takes the time to do things properly and efficiently. I'm sure I could slap together some managed app in no time, but it would never be satisfying to become a "VB Programmer". .NET is also an issue because MS doesn't have a good track record of playing nicely. If you take the devil's money, even with the best intentions, you'll still end up burnt.

    14. Re:An interesting read on the subject by shutdown+-p+now · · Score: 2, Informative

      Then there's the technical aspect that mono will always be running behing the microsoft C#/CLI version

      That's assuming that one cares. Try to consider Mono as a platform of its own, forgetting about .NET entirely. It really makes much more sense that way (because then you can also consider Gtk# and other nice Mono-specific APIs).

      nd so your Linux mono application will generally not even run on Windows

      The easiest way to run your Linux Mono application on Windows is to run it in Mono for Windows...

      If one wants to develop great crossplatform apps, use Qt [qtsoftware.com], it has all and more of the advantages, and none of the risks.

      It has the disadvantage that it's a C++ toolkit, with all the associated problems such as overcomplicated (for most) language, and limited quality of tooling. There's a reason why higher-level languages such as Java and C# were introduced.

      That said, Qt really tries hard to look a lot like Java, so it's not as hard to deal with as C++ can generally be. And Qt Creator is a very decent C++ IDE.

    15. Re:An interesting read on the subject by PitaBred · · Score: 1

      They haven't done it yet. But Microsoft hasn't really given most of us a good reason to trust them... why should we now? Because Freetardo Jones, who for all we know is an MS employee, says so?

    16. Re:An interesting read on the subject by kelnos · · Score: 1

      I don't dislike C# because I think it's a bad language (I don't know enough about it to form an opinion); I dislike it because it's an extension of a possibly-encumbered Microsoft technology. I don't trust Microsoft. I see no need to do anything with C# while there are other technologies that do everything I need without tying me to something with a murky future, controlled by a company I don't trust.

      --
      Xfce: Lighter than some, heavier than others. Just right.
    17. Re:An interesting read on the subject by BRSloth · · Score: 1

      This is bullshit. Every app I've written against Mono that doesn't use any of their extensions has run perfectly on .NET on Windows. Just so you know, Mono supports pretty much all of the important parts of .NET 3.5 so I don't know where you are pulling this shit from.

      Try the other way around. Wake me up when things compiled with Microsoft C# compiler works on OS X.

    18. Re:An interesting read on the subject by Alioth · · Score: 1

      It's likely because Microsoft will soon hold patents (they have outstanding patent applications) on technologies that Mono includes. Given that Microsoft has openly declared themselves as being the arch-enemy of Linux, it seems foolish to make Linux distributions depend on a technology that Microsoft owns - because if programs depending on Mono get popular to such an extent the Linux desktop now heavily depends on it, Microsoft can just turn around and destroy Linux on the desktop with a patent lawsuit.

      Additionally, Mono will always trail .NET, and will always be the poor second class relation of .NET if you're trying to develop cross platform programs. On the other hand, despite its faults, you're still a first class Java citizen if you use Java on Linux - you're not playing catch-up to some other implementation of Java. You have the same, complete implementation that everyone else has.

      I'm sure Mono is very good, but at the moment it contains a fairly fatal legal flaw which renders it dangerous to free software.

    19. Re:An interesting read on the subject by Anonymous Coward · · Score: 0

      How much M$ is paying to you?

    20. Re:An interesting read on the subject by yossarianuk · · Score: 1
      Maybe they are saving Ajax for another day.... In fact you may be giving the enemy ideas.

      A small counterpoint: XMLHttpRequest, the base call behind al things AJAX, is MS-originated; but it has evolved from that, and it's a widely complied de-facto standard. In fact, IE8 accepts the non-MS variant.

  11. Re:Yessss by recoiledsnake · · Score: 3, Informative
    --
    This space for rent.
  12. Re:Slow news day by JSBiff · · Score: 3, Insightful

    Proven? Really? What's the proof? That Microsoft hasn't sued yet? That doesn't stop them from suing in the future. I'm not aware of any 'proof' that the Mono fear is stupid. If anything, I used to not be too worried about Mono, until Microsoft sued TomTom for their use of Linux. That was NOT a lawsuit over Mono, but rather over VFAT and some other stuff. But, it proved that Microsoft is willing to use stupid patents to sue Linux users. So, now I'm worried that in the future, they will decide to sue over Mono. What would stop them if they should decide to sue?

  13. Re:Yessss by Anonymous Coward · · Score: 1, Interesting

    Open and Closed source worlds are not exclusive and can happily co-exist with each other.

    You mean a closed source browser can access an open source web server (or vice versa)? Sure. No one in the FSF is trying to prevent that, as far as I know. But if Microsoft decides to use its patent portfolio to pull the plug on Mono then there's a problem for all of us. Looks like the "stallmanists" might be on to something after all! Like it or not, you can't guarantee that Mono will still be legal next year.

  14. Another good reason to use KDE by Anonymous Coward · · Score: 5, Funny

    GNOME folks are really pushing the adoption of KDE 4 nowadays.
    It is great to see so much friendship between open-source projects :)

    1. Re:Another good reason to use KDE by Anonymous Coward · · Score: 0

      Given that KDE 4.2 is still hideously slow and buggy, I guess it needs to be pushed.

  15. Re:Victory for Free Software Advocates by Aphoxema · · Score: 1

    I don't see how this wins anyone anything.

    --
    "Most people, I think, don't even know what a rootkit is, so why should they care about it?"
  16. 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.

  17. Re:Slow news day by Freetardo+Jones · · Score: 1

    So how many more years of them not suing anyone over Mono is it going to take before you people finally calm down and shut the fuck up? We've heard for 5 years this constant drumbeat that Microsoft is always around the corner waiting to sue people for Mono and none of you Chicken Littles have been right. Seriously, Microsoft deserves criticism for many things they have done in the past, but they have done right by this and have been about as open and willing to work with the FOSS community on Mono as one can really expect from a company like this.

  18. 50 MB? by Anonymous Coward · · Score: 0

    The last time someone came up with accurate figures, it was a 10 MB difference between including GNote and Tomboy.

    1. Re:50 MB? by Anonymous Coward · · Score: 0

      That's the delta between apps. If you don't use any other Mono app, though, there's a ~50Mb delta instead.

  19. When taking a stand... by ketilwaa · · Score: 1

    When taking a stand towards something, I find it sometimes useful to look at the people being very for or against. Viewing some of the comments from anti Mono people like this, makes in itself a good case for being sceptical towards the anti crowd in this case.

    To me, GNU/Linux is not a handful of fledgling arms and tinfoil hats, and that is excactly what I see from a lot of the anti Mono people.

    1. Re:When taking a stand... by jedidiah · · Score: 1

      Microsoft has been abusing competitors and PARTNERS alike since it was founded.

      The only irrational position here is to ignore that fact.

      No weak insults will change that.

      Get in bed with Microsoft and you have to be careful that you don't
      end up with a knife in your back and act accordingly. If you go into
      such a partnership with blinders then bad things will happen.

      Play with fire if you must. Just acknowledge that you are doing so.

      Although nothing has really seemed to come of this flirtation so far.

      Mono? Forget Mono. Install KDE4 by default. There are some interesting KDE apps.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    2. Re:When taking a stand... by bluefoxlucid · · Score: 1

      My whole issue with Mono and Java revolves around technical aspects of the implementations. They are purely data-code confusion: your executable code is data.

      For perspective, a normal application has a .text (code) segment and .bss (data) segment. There's other stuff but let's keep this simple. When the application loads, .text gets mmap()ed into memory as the main executable or a library area (for shared objects), while .bss gets mapped as the heap or as library data (for shared objects). When the same object gets mapped into memory by multiple programs, it gets shared until one side or the other alters it.

      By contrast, a VM application loads the VM the same way, and then loads the application on top of it. The application ships data (data) and code (data). The 'code' gets translated into native instructions, which get executed. Each copy of the program maps the files shared; but the code itself is private anonymous memory, meaning 50 copies of the same library loaded in different programs puts 50 copies in physical RAM, instead of 1 shared copy. Further, whenever the code gets generated or altered, the processor has to shift it between the Dcache and the Icache, causing a mess and some minor performance issues; multiprocessor systems especially have some confusion with this sort of behavior, due to cache coherency algorithms and the need for processors to have a vague idea of what other processors are doing with memory.

      Further, all of these solutions supply functionality through native code, both in the base VM and in libraries like Libpng and Libogg. In normal operation, we can make non-executable memory non-executable (i.e. mprotect(...|PROT_EXEC, ...) fails on non-executable memory segments), and executable memory non-writable (i.e. mprotect(...|PROT_WRITE|PROT_EXEC, ...) fails). This used to be a PaX/Grsecurity thing, but SELinux has this functionality now. The problem is we can't apply this to any address space associated with a VM; we could improve SELinux policy a bit and apply protections to everything but anonymous mappings, but that creates an approximately sealed environment. There are other methods to tighten the seal, but none to perfectly seal a VM.

      What all this means is Mono and Java applications consume more memory (due to lack of sharing) and are less secure than native C applications, due to susceptibility to buffer overflow and other bugs in the VM itself and bound native libraries that lead to code injection. Mind you, the default configuration of a normal Linux system doesn't apply the tight security constraints we'd like to see; but they're impossible to apply fully to any process running a VM, because these constraints rely entirely on blocking all paths that lead to runtime-generated code execution.

      And yes, Mono is made by Microsoft, blahblahblah, evil empire, fucking kill google, whatever. See above for worthwhile arguments.

    3. Re:When taking a stand... by ketilwaa · · Score: 1

      Thanks for including a coherent and actually interesting view of what this whole thing is about. Screaming "M$ are trying to pwn us!111!!" like so many seem to be doing is not a valid argument, and you sir, take a different path, and I commend you for doing so.

    4. Re:When taking a stand... by bluefoxlucid · · Score: 1

      I enjoy constructing critical arguments when everyone else is just bitching incoherently about something. Also I like concrete, factual arguments; if someone claimed I was the father of their child, I would be more inclined to present papers showing I'd had a vasectomy years prior, rather than arguing about if we did or didn't have sex (even if we never did). I mean come on, did we have sex? ... does it matter? You can't argue with that. You can't argue with my analysis of Mono either; you can either accept the drawbacks or reject Mono.

    5. Re:When taking a stand... by Super_Z · · Score: 1

      People are afraid of a rerun of this story. Accusing people vary of Microsofts motives of "wearing tinfoil hats" strikes me as a bit naive.

    6. Re:When taking a stand... by Ant+P. · · Score: 1

      I'd call myself anti-Mono, but only because I've actually tried to use it. Trying to load a folder of 100 camera JPEGs into F-Spot (on a Core 2 Duo with 4GB of RAM), and then seeing the entire GUI lock up for 3-4 minutes isn't my idea of a user friendly experience. For the GNOME Project, evidently it is.

    7. Re:When taking a stand... by ketilwaa · · Score: 1

      I sure hope you base your decision on more than that. Otherwise I'd be anti every type of programming language, because of the bugs I've seen in various applications. I personally think F-spot sucks bigtime, so I don't use it. I think other applications like Gnome Do and Tomboy are great. So, your gripe with F-spot is not necessarily due to Mono, but could very well be due to poor use of it.

    8. Re:When taking a stand... by telemachuszero · · Score: 1

      I'd call myself anti-Mono, but only because I've actually tried to use it. Trying to load a folder of 100 camera JPEGs into F-Spot (on a Core 2 Duo with 4GB of RAM), and then seeing the entire GUI lock up for 3-4 minutes isn't my idea of a user friendly experience. For the GNOME Project, evidently it is.

      "For the GNOME Project"? Why not say "for the F-Spot developers"? It uses the gnome libraries, but it's not an official gnome application. Also, the current version is 0.5.0.3. Evidently the developers don't think it deserves to be marked 1.0 yet either. You can no doubt find badly implemented applications in nearly any language and framework around.

  20. Re:Good by Anonymous Coward · · Score: 2, Funny

    Python is awesome. Linux is better for having it around.

    Fixed it for ya.

  21. what a troll by jipn4 · · Score: 5, Informative

    Apparently, Debian doesn't have the same concerns over using specifications patented by Microsoft and licensed under undisclosed terms

    Microsoft has filed a patent on the .NET APIs, but Tomboy (and most Mono applications) don't use the .NET APIs, they use the ECMA APIs and standard Linux APIs. Mono is no different in that way from Python, Ruby, Perl, or many other languages people commonly use on Linux: it uses proprietary APIs on Windows, and open source APIs on Linux.

    Furthermore, Mono is way ahead of languages like Java in that regard because, unlike Java, Mono is based on an open standard and there are no known patents on the language core or core libraries.

    If anybody can point to an actual patent that Mono or Tomboy violate, please file an issue report against the Mono project; if it is credible, the infringing functionality will be removed from Mono. So far, nobody has been able to come up with anything.

    1. Re:what a troll by seanbeeson · · Score: 1

      I have to totally agree with you that this debate has been gone over so many times that it is a troll posting. Please read the following.... Started by another troll on the mono list anonymously under the name 666lawyer: http://lists.ximian.com/pipermail/mono-list/2009-June/042680.html From some time ago... http://www.jprl.com/Blog/archive/development/mono/2009/Jan-19.html Here we go again...Why Mono doesn't Suck... http://www2.apebox.org/wordpress/rants/124/

    2. Re:what a troll by 0xABADC0DA · · Score: 4, Informative

      Furthermore, Mono is way ahead of languages like Java in that regard because, unlike Java, Mono is based on an open standard and there are no known patents on the language core or core libraries.

      Java is based on an open standard... the fully open-source reference JDK.

      The reference JVM is also significantly faster than mono and somewhat faster than Microsoft CLR and has loads of somewhat useful other languages implementations that compile to it (Ruby, Python, Scala, Groovy, etc). So I'm not sure where you're pulling "way ahead" from.

    3. Re:what a troll by bcrowell · · Score: 2, Insightful

      unlike Java, Mono is based on an open standard

      This is literally true, but very misleading. Microsoft has ECMA bless .NET from time to time. Java has the Java Community Process. Yeah, sure, ECMA calls itself a standards organization, and the Java Community Process doesn't. If you look back at the history of Java, its big selling point from the beginning was that it was cross-platform, Sun fought intensely to make sure that it didn't get turned into a nonstandardized mess by MS, and Oracle's reference implementation is GPL'd. Microsoft, on the other hand, has demonstrated with OOXML that they see standards bodies as things that they can cynically manipulate.

    4. Re:what a troll by Anonymous Coward · · Score: 0

      > Microsoft has filed a patent on the .NET APIs, but Tomboy (and most Mono applications) don't use the .NET APIs, they use the ECMA APIs
      ECMA is a standard body and IS NOT an API similar to .NET. There's not such thing as ECMA APIs in your context
      Microsoft submit C# to ECMA for open standard. This doesn't prevent them from filing a patent on its implementation at the same time. You can have an open standard with patent like OOXM, PDF, etc

      > Mono is no different in that way from Python, Ruby, Perl, or many other languages people commonly use on Linux: it uses proprietary APIs on Windows, and open source APIs on Linux.
      This is incorrect. First of all, Python, Ruby, Perl are languages. Mono is a framework like .NET. The language you are looking for is C#
      Secondly, Python, Ruby and Perl do not have core that are patent ambiguous. There are .NET implementation for Python and Ruby called IronPython and IronRuby.
      Mono is just a direct implementation of .NET which is patented.

      > If anybody can point to an actual patent that Mono or Tomboy violate, please file an issue report against the Mono project
      Do you know all of Microsoft patents? I guess not. Until then why should Linux take the risk when Balmer is touting that Linux violated 200+ Microsoft's patent.

      >So far, nobody has been able to come up with anything.
      So far nobody has been able to come up with the 200+ Linux was claimed to violated. Your statement prove absolutely nothing.

      I think you need to get your facts right before you identify who the troll is.

    5. Re:what a troll by tuomoks · · Score: 1

      Yep - an API is an API but still, how can you patent an API, some of my APIs before Microsoft even existed look a lot like some in .NET, Windows, whatever - who cares? Anyway - MONO is just one subsystem, what's the big deal? You don't like it, as I don't, use something else. I find MONO, .NET, etc bloated, full of stupid decisions, mostly slow, made for inexperienced programmers who need someone holding their hand, who (still) live in dreams that technology is more important than thinking and design, etc - or for managers who really don't know better but believe everything the vendors (the larger vendor, the better) feed to them or, a credit for .NET and ilk, for some CS persons who are too lazy to create anything by themselves but need something for next term paper, grad paper, whatever.

      Another problems I see here is that MONO, .NET, Java, Python, Windows, Linux, etc are compared as equals - they all are very different things. Yes, I know, even Microsoft hasn't yet made up their mind what .NET (and MONO) really is - it definitely is not a language but it also definitely is not an architecture or even a common framework but neither is Java. And maybe it is something great what we haven't seen yet? I personally love to follow frameworks and architectures but as building blocks for systems to stay in as simple components as possible. This just by long experience, makes life much easier! After reducing the system size and code base always over 50% in command level CICS (who knows what that is?) or Pathway or whatever transaction systems, in big (state/country wide) .NET wireless systems and/or Java/web mess, etc with great pain, fixing their "managed" / controlled memory and other performance problems caused by "experienced specialists", etc any simple (not simple by functionality but by design/manageability) gets my vote.

      Back to the subject, MONO is not bad by itself, the code actually shows that the developers (mostly) know what they are doing, it may bring more users to Linux (not that anybody cares but..), it actually challenges Microsoft instead of giving them more benefits / control they already have, and so on.

    6. Re:what a troll by slack_justyb · · Score: 1

      If anybody can point to an actual patent that Mono or Tomboy violate, please file an issue report against the Mono project;

      I know it is a bit old but, we'll file one once they publish which part they're going to patent, of course, that shouldn't be long. PS: The only complaint I have of .NET is the syntax of LINQ, but what'cha going do?

      Besides, anyone thinking that MS would attacking Linux using patents isn't giving Microsoft any credit. I figure that they would try to kill Linux (GNOME proper, since GNOME != Linux) via contracts with Linux vendors as opposed to patents. It just seems too obvious to go that (patents) route. Linux isn't the problem with MS, it is more like the vendors pandering Linux that is.

      Also I develop on OpenJDK, I was wondering if you could provide a list of patents that the OpenJDK is infringing on? I'm sure we could work out what it is that you feel is something we may have overlooked.

      Mono is way ahead of languages like Java in that regard because, unlike Java, Mono is based on an open standard

      Could you clear that up? I'm not sure I follow what you are talking about. Is it because .NET is a standard through an organized body? Whereas, Java is basically a community process with Sun at the head of the community? If this is your beef with Java then what exactly is different between how Java is made versus something like, Linux or GNU HURD?

      Besides, what is all this seemingly bad blood between .NET and Java? I've been to many PDCs and the people behind .NET seem pretty accepting of Java much like the Samba - Microsoft love (which granted isn't awesome but it is still pretty good). Also, the Mono devs are pretty cool people on IRC. Really? Do we need to build walls?

    7. Re:what a troll by PsychicX · · Score: 1

      Just FYI, an open source reference implementation is NOT a standard, nor does it imply the existence of an open standard. So you may want to mention ACTUAL standards instead.

    8. Re:what a troll by Anonymous Coward · · Score: 0

      This is literally true, but very misleading.

      I don't think it's misleading at all. C# has gone through a standards process with a recognized standards organization. The JCP is simply something Sun has designed for its own convenience.

      If you look back at the history of Java, its big selling point from the beginning was that it was cross-platform, Sun fought intensely to make sure that it didn't get turned into a nonstandardized mess by MS, and Oracle's reference implementation is GPL'd.

      Sun has been using the JCP, their intellectual property, and their licensing strategy to force companies to license commercial versions of Java from Sun and drive all alternative Java implementations out of business.

      Microsoft, on the other hand, has demonstrated with OOXML that they see standards bodies as things that they can cynically manipulate. ... whereas Sun cynically lied to the Java community about their intentions for standardization and then pulled a bait-and-switch. Sorry, however bad the OOXML standard may be (and I think it's pretty bad), it still beats no published standard at all.

    9. Re:what a troll by Anonymous Coward · · Score: 0

      Hello, it's Mr. Reading Comprehension Helper here!

      The parent comment was referring to Mono being way ahead *in openness* and did not make any reference to technological progress.

      (As a side note, a nitpicker would say that the "open standard" Java is standardized on its TCKs, not a reference implementation. And the TCKs are not necessarily fully open.)

    10. Re:what a troll by Anonymous Coward · · Score: 0

      This doesn't prevent them from filing a patent on its implementation at the same time. You can have an open standard with patent like OOXM, PDF, etc

      You can, but ECMA C# is not covered by Microsoft's patent. Microsoft's patent covers .NET.

      This is incorrect. First of all, Python, Ruby, Perl are languages. Mono is a framework like .NET. The language you are looking for is C#

      Python, Ruby, and Perl are both languages and libraries, just like Mono.

      Secondly, Python, Ruby and Perl do not have core that are patent ambiguous.

      Neither does Mono.

      Mono is just a direct implementation of .NET which is patented.

      That is incorrect. Mono has many libraries and frameworks. One of those happens to be a bunch of .NET libraries that Microsoft has filed a patent or. Those libraries are not used as part of Tomboy or any of the other Mono desktop applications; they aren't even installed.

      Do you know all of Microsoft patents? I guess not.

      I don't have to know all the patents myself (although I have done a number of searches for relevant patents). There are at most a few hundred patents that could be relevant and they have been scrutinized extensively by the community.

      So far nobody has been able to come up with the 200+ Linux was claimed to violated. Your statement prove absolutely nothing.

      I don't have to "prove" that Mono is free from Microsoft patents, since nobody can prove that about any other language; any open source project runs a risk of patent infringement. Microsoft may have patents on technologies in Java, Python, C++, or whatever other language you favor.

      But as far as Mono is concerned, the issue of Microsoft patents has received so much scrutiny that, if anything, Mono is less likely to have patent problems than any other language.

      I think you need to get your facts right before you identify who the troll is.

      You need to get YOUR facts straight.

    11. Re:what a troll by jipn4 · · Score: 2, Insightful

      I know it is a bit old but, we'll file one once they publish which part they're going to patent

      The patent system doesn't work that way. Anything that they could possibly patent would have had to have been filed years ago and is publicly available now.

      Is it because .NET is a standard through an organized body? [ecma-international.org] Whereas, Java is basically a community process with Sun at the head of the community? [jcp.org]

      Yes. Sun, in fact, promised ISO, ANSI, and then ECMA standardization. They reneged on those promises because it forced them to open up the language too much, which tells you that the JCP is not a standards process. From a practical point of view, I think the JCP has pretty much destroyed Java.

      If this is your beef with Java then what exactly is different between how Java is made versus something like, Linux [lkml.org] or GNU HURD? [gnu.org]

      Linux and the Hurd are not standards, they are open source projects. Sun Java, likewise, isn't a standard, it's a dual-licensed project.

      Besides, what is all this seemingly bad blood between .NET and Java?

      I don't know about .NET, since I don't use it. I do use Mono. In any case, I really don't care whether people use Java, but Java is a good example to contrast with Mono because many people regard it as "open", yet it is far more encumbered than ECMA C# or Mono: Sun owns key parts of the Java specifications and they have numerous patents on core Java and the libraries. If that doesn't bother open source developers, why should using Mono bother any open source developer?

    12. Re:what a troll by Anonymous Coward · · Score: 0

      The parent comment was referring to Mono being way ahead *in openness* and did not make any reference to technological progress.

      Mono: open standard, closed reference VM, closed reference library

      Java: open standard (de-facto), open reference VM, open reference library

      Java wins hands down on openness and it is better tech and has better alternative languages. There's a reason why mono advocates tend to be rabid, because otherwise they wouldn't be using mono. They'd be using some combination of a JVM language or C/C++ or python/ruby/javascript.

    13. Re:what a troll by Vahokif · · Score: 0

      A reference implementation isn't a standard, and all the languages you mentioned compile to .NET too (and more, including Java itself) as .NET was designed from the start to be language-agnostic.

    14. Re:what a troll by Anonymous Coward · · Score: 0

      I think you can't patent an API, but only the implementation of it.

    15. Re:what a troll by slack_justyb · · Score: 1

      I think the JCP has pretty much destroyed Java.

      I think quite differently. The JCP has brought us things like JOGL, JAXP, and many more advancements of the Java technology.

      They reneged on those promises because it forced them to open up the language too much

      Because Sun saw fit to prevent Microsoft from making a bastard version of Java? Because such a version would have destroyed the entire point of Java, Write once/Run everywhere? Much like their MS LDAP? (I mean Active Directory.)
      Moot point now that Microsoft has their own Java, er, Runtime.

      they have numerous patents on core Java and the libraries.

      Do you care to point them out? And how OpenJDK has worked around those?

      why should using Mono bother any open source developer?

      Because Microsoft is a big software bully. Really, however, the implementation of Mono works around the tricky parts much like OpenJDK does. I know all too well the pain that Mono devs must face. OpenJDK gets dogged for, "Always being behind the one true JVM," or "Java is a patent trap, GPLv2 wasn't enough, now we're making exceptions?!" In the end, I don't think that I'm your target audience for that question because I think Mono does enough to protect itself.

      I don't know about .NET, since I don't use it. I do use Mono...but Java is a good example to contrast with Mono because many people regard it as "open"

      Java like .NET is a platform. Sun's Java implementation is to Microsoft's .NET implementation as OpenJDK's Java implementation is to Mono's .NET implementation. I can see that you can tell the difference between MS .NET and Mono .NET, I hope I've cleared up the comparison for JVMs as well.

    16. Re:what a troll by shutdown+-p+now · · Score: 1

      The reference JVM is also significantly faster than mono and somewhat faster than Microsoft CLR

      Mono JIT and GC are slow as molasses compared to both JVM and .NET. The rest of it is not as clear-cut, however.

      In general, it is accepted wisdom that Java has 1) a better optimizing JIT; and 2) a more advanced GC. In practice, however, .NET often ends up being faster, simply because the languages and the platform itself offer more optimization opportunities. For example, .NET has value types, and standard class library uses them a lot - and they are obviously more efficient for specific cases. For Java to match this, it has to do escape analysis to determine where heap-allocated reference types are effectively used as if they were value types. Other examples include all methods in Java being virtual by default (whereas it's opt-in in .NET).

      and has loads of somewhat useful other languages implementations that compile to it (Ruby, Python, Scala, Groovy, etc). So I'm not sure where you're pulling "way ahead" from.

      Language-wise, both platforms are doing pretty well. For comparison with your list, .NET has IronPython (which is in fact more up-to-date than Jython), IronRuby (which is still in alpha and generally less stable than JRuby), F#, and Boo.

    17. Re:what a troll by shutdown+-p+now · · Score: 1

      C# and CLI specs (corresponding to .NET 2.0) are ISO standards, not just ECMA ones.

    18. Re:what a troll by z121212mlmiac · · Score: 1

      Mono does have implementations of non-standard .NET features, such as System.Windows.Forms. These might have patents. Tomboy (and most Mono apps written for use on Unix-like systems) don't use them, but that doesn't magically make their implementations disappear.

    19. Re:what a troll by Anonymous Coward · · Score: 0

      Another problems I see here is that MONO, .NET, Java, Python, Windows, Linux, etc are compared as equals - they all are very different things. Yes, I know, even Microsoft hasn't yet made up their mind what .NET (and MONO) really is

      Microsoft doesn't get to make up their mind about what Mono is. Mono is what it is: an ECMA C# implementation (compiler and core libraries), a lot of bindings to standard open source libraries (e.g., Gtk+, Gnome), and an optional compatibility layer for some .Net libraries.

      Some of these may infringe someone's patents--Microsoft's, IBM's, Sun's, Apple's, Patent Troll Inc.'s, etc.; nobody knows. But that's no different from any other large software system, which is why people keep mentioning large software systems.

      The only unusual thing is that there is one Microsoft patent application that could possibly affect the compatibility layer. But that doesn't really matter to most people because that compatibility layer isn't used by native Linux desktop applications written in Mono. It certainly doesn't affect Tomboy, Banshee, Gnome Do, or any of the other common desktop apps written in Mono.

    20. Re:what a troll by jipn4 · · Score: 1

      I think quite differently. The JCP has brought us things like JOGL, JAXP, and many more advancements of the Java technology.

      If you consider OpenGL and XML parser bindings "advancements", then Java technology is really starting very low.

      Because Sun saw fit to prevent Microsoft from making a bastard version of Java? Because such a version would have destroyed the entire point of Java, Write once/Run everywhere? Much like their MS LDAP? (I mean Active Directory.)

      Who cares what reasons Sun gave? The result is the same: Java is not an open standard.

      Do you care to point them out?

      Go search on Google Patents; they are say enough to find.

      And how OpenJDK has worked around those?

      It doesn't have to; Sun has made those patents specifically available for "OpenJDK" under the GPL. However, everybody else has to license their patents. That's one of the things that makes Java not an open standard.

      Because Microsoft is a big software bully.

      Sun/Oracle is a big software bully, too. And Microsoft can sue over OpenJDK, Sun/Oracle can sue over Mono, and IBM can sue over both.

      Java like .NET is a platform.

      Yes. They are also brand names.

      Sun's Java implementation is to Microsoft's .NET implementation as OpenJDK's Java implementation is to Mono's .NET implementation.

      Not at all. Sun Java and OpenJDK are largely the same codebase and share most of their APIs. Microsoft .NET and Mono are completely different implementations and share almost no APIs on the default installs. Mono happens to have a set of .NET compatibility libraries, but those are neither needed nor used much.

      I can see that you can tell the difference between MS .NET and Mono .NET, I hope I've cleared up the comparison for JVMs as well.

      You need to clear up your confusion if you think that there is more than one Java implementation in the world. All there is is Sun Java and its derivatives.

    21. Re:what a troll by slack_justyb · · Score: 1

      If you consider OpenGL and XML parser bindings "advancements", then Java technology is really starting very low.

      As two examples, but I'm sure you can head over to JCP and see everything that they have done. But I'm guessing you won't.

      Who cares what reasons Sun gave? The result is the same: Java is not an open standard.

      Your idea of "open" misses the idea of "open." However, I'll just fault whoever it was that taught you what "open" means, since you do no research yourself.

      Go search on Google Patents; they are say enough to find.

      See last point given.

      ...specifically available for "OpenJDK" under the GPL. However, everybody else has to license their patents.

      Please head over to here and read. I know that may be quite a task for you.

      Sun/Oracle is a big software bully, too.

      And who is it again that was found to be an abusive monopoly? I'll let you research that one too.

      Yes. They are also brand names.

      Any other small facet of their names that has no meaning on the conversation you'd like to bring up as well?

      Sun Java and OpenJDK are largely the same codebase and share most of their APIs.

      Please read what the difference between ABI and API are. Thank you.

      All there is is Sun Java and its derivatives.

      Call me a troll and mod me down like a motherfucker, but I'll have to call it like I see it and call you an idiot or you really like to pull people's legs.

    22. Re:what a troll by man_of_mr_e · · Score: 1

      Mono: open standard, closed reference VM, closed reference library

      Untrue. Microsoft released, many years ago, an open source (BSD Licensed) Reference platform and library.

      Java: open standard (de-facto), open reference VM, open reference library

      False. Java is only a de-facto standard. "Open standard" means it's been standardized by an open standards body, such as OASIS, ECMA, ISO, etc.. Further, Not all of Java is open sourced, there are still significant portions that have not been opened.

      Better alternative languages? Non-Java languages are not supported by Sun. In comparison, Microsoft publishes and supports half a dizen languges themselves and openly solicits other languages (like Eiffel, for instance) of which there are literally hundreds.

    23. Re:what a troll by Anonymous Coward · · Score: 0

      An open source reference implementation does not equal an open standard.

    24. Re:what a troll by man_of_mr_e · · Score: 1

      This is literally true, but very misleading. Microsoft has ECMA bless .NET from time to time

      And of course ISO as well. You did know that C# and the CLI are ISO standards as well, right?

      Sun attempted to put Java through the PAS system 2 or 3 times, but pulled out every time, pissing off people that had done a lot of work and ended up with nothing.

      JCP is meaningless. It's an advisory board. Sun has no requirement to listen to the JCP.

    25. Re:what a troll by man_of_mr_e · · Score: 1

      ECMA is a standard body and IS NOT an API similar to .NET. There's not such thing as ECMA APIs in your context

      You're being obtuse. He clearly means the API's that are published by ECMA as ECMA standards.

      Microsoft submit C# to ECMA for open standard. This doesn't prevent them from filing a patent on its implementation at the same time. You can have an open standard with patent like OOXM, PDF, etc

      There are no known patents on ECMA C# or CLI, or their ISO versions. That doesn't stop MS from filing a patent that may cover it in the future, but as of right now, nobody has found any. But then, Anyone can file a patent on any technology. All they have to do is prove they did it first (the patent can come years afterwards).

      Secondly, Python, Ruby and Perl do not have core that are patent ambiguous

      Neither does ECMA/ISO C# and CLI. Yes, Microsoft has some patents on things to do with web services and other parts of the Windows stack, but not the ECMA/C# stuff. This is pure FUD. "Microsoft *might" do this, or they *may* have that". It's the definition of FUD.

      Mono is just a direct implementation of .NET which is patented.

      No, Mono is a direct implementation of ECMA/ISO C#/CLI, which is *NOT* patented. They also do implement some of the Windows stack, but they seperate that code and you are free to not use it if you want a patentless stack.

      Do you know all of Microsoft patents? I guess not. Until then why should Linux take the risk when Balmer is touting that Linux violated 200+ Microsoft's patent.

      So, if you're going to accept that Microsoft may have patents on Mono, why do you reject that Microsoft may have patents that cover Linux? That's an illogical argument.

      By your way of thinking, you should completely throw away Linux because Microsoft claims they have patents on it.

    26. Re:what a troll by Svartalf · · Score: 1

      No, you can't patent an API, but if there's a narrow range of usable implementations, you CAN (As long as In re Bilski hasn't
      been heard and upheld by the SCOTUS...then this changes a bit...) patent the range thereof, effectively barring any outside implementations
      of said API...

      --
      I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
    27. Re:what a troll by jipn4 · · Score: 1

      As two examples, but I'm sure you can head over to JCP and see everything that they have done. But I'm guessing you won't.

      I was a Java developer for over a decade and still develop in it occasionally, painful as that is. Take it from me: the JCP has produced enormous bloat and few innovative APIs.

      Your idea of "open" misses the idea of "open." However, I'll just fault whoever it was that taught you what "open" means, since you do no research yourself.

      No, your idea of "open standard" misses the idea of "open". "Open standard" means that anybody can implement and use it for any purpose, without having to get special permission from the originator of the standard. Java cannot be implemented that way because you need to pass Sun's compatibility test and because the specifications themselves are owned by Sun.

      Call me a troll and mod me down like a motherfucker, but I'll have to call it like I see it and call you an idiot or you really like to pull people's legs.

      You're a victim of Sun marketing and brainwashing. Sun promised an open standard, ISO/ANSI standardization, and cross-platform functionality. What they delivered was a proprietary platform, the JCP, and worse cross-platform capabilities than Tcl/Tk, plus a lot of marketing to confuse gullible people like you.

    28. Re:what a troll by jipn4 · · Score: 1

      Java is based on an open standard... the fully open-source reference JDK.

      The purpose of a reference implementation is to serve as a reference for independent third party implementations that illustrates behavior (reference implementations are typically simple, clean, and low performance). It's more than a decade after Java first appeared; where are the independent third party implementations that use OpenJDK as a reference?

      In order for it to be a reference implementation, it would have to be a reference implementation of a standard, but there is no Java standard. That's because the only way you can actually implement Java without infringing on Sun's intellectual property is if you pass their compatibility tests. For practical purposes, you can't do that unless you actually sign a license agreement with them. That's why Microsoft developed .NET and Google developed Dalvik, deliberately incompatible implementations that work around Sun's intellectual property.

      As for OpenJDK, you have two choices: you can use it under the GPL, which precludes many commercial uses, or you can license it from Sun.

      Of course, it is good that we have the "OpenJDK" under the GPL now, compared to the situation before that. But that's not the same as Java being an "open standard". Compared to most other programming languages, Java is one of the most legally encumbered languages in existence.

    29. Re:what a troll by slack_justyb · · Score: 1

      No, your idea of "open standard" misses the idea of "open"...you need to pass Sun's compatibility test and because the specifications themselves are owned by Sun.

      By that standard, project's like OpenGL and x86 fail to be open standards. However, if we simply use your flawed definition of "open" then you are correct.

      Sun never went to ISO, ANSI, or ECMA. Sun requires that you pass the compatibility test in order to slap the label of Java on your product. Sun owns the spec to the Java platform. All of this is true, but it's pulling a Slashdot and twisting the facts to make it look like some evil is going on here.

      Oh and by the by: Just for comparison, how many people has Sun brought in for litigation or wiped off the face of the Earth? Now ask yourself, how many has Microsoft done the same?

      No one requires you to call your implementation Java, much like how Mesa is not OpenGL. The Java standard is owned and controlled by Sun to protect Java from, well basically, Microsoft. When Microsoft showed no more interest in Java as a platform and came up with their own, it's funny how that GPL of the source code came soon after. I'm sure that if we had more time with Sun Microsystems they would have looked into going to ECMA or ISO for a standard, if only to just show up Microsoft's platform.

      I was a Java developer for over a decade and still develop in it occasionally

      I am a Java developer and I have been working with Java since 1997, that would put me at 12 years working with Java. You can take that to mean whatever it may be worth to you.

      Take it from me: the JCP has produced enormous bloat and few innovative APIs.

      Wow, and ECMA or ISO approved things never get any bloat! Let the C++ people know that export keyword isn't useless.

      That's a totally subjective point of view and totally misses the fact that most platforms accrue tons of weight as they age. You're not required to use the dead weight, I'm not seeing your point here. The JCP has added much value to Java from it's infant state back in 1992. Again, that's totally subjective. I won't call your wrong on it but I won't call your right either.

      worse cross-platform capabilities than Tcl/Tk, plus a lot of marketing to confuse gullible people like you.

      I've not had an issue with cross-platform. However, I do know some people who have used JNI to bind specific interfaces that tie them down. I've gone from AS400 to Windows 2000 Server to Linux with the exact same bytecode that was written in 1999. I've had to change none of the core code. Things like JPA to databases have had to change since we've changed database vendors, but I hardly fault Java for that. That's also considering that the core code for the EJB(s) was written before Sun officially accepted EJB from IBM. That's right EJB was invented by IBM not Sun as you may like to think.

      Obviously you've had a bad taste of Java. That's fine, maybe it wasn't for you. From where I stand it's a very good platform and has met my needs countless times. It meets what I consider to be an open standard, given the market environment it has had to work in, and it works on the machines and architectures that I use. There are FOSS advocates that support the Java platform and it is used in a lot of the businesses that I have worked for.

      I doubt that it is the marketing that has confused me as we all know that Sun sucks in the marketing department, hence the selling out to Oracle.

      Finally, I don't want anyone to get me wrong. .NET and Mono are great advancements in computers. I encourage everyone to find the product that best fits their needs. However, calling Java not-open and .NET more open is just Java bashing, pure and simple. I would hate to think that the .NET people have nothing to bash Java on except the fact that they didn't go to a standards body and instead opted to form their own community process.

    30. Re:what a troll by jipn4 · · Score: 1

      By that standard, project's like OpenGL and x86 fail to be open standards. However, if we simply use your flawed definition of "open" then you are correct.

      Quite incorrect. Both OpenGL and x86 have multiple independent implementations. Java does not.

      Oh and by the by: Just for comparison, how many people has Sun brought in for litigation or wiped off the face of the Earth? Now ask yourself, how many has Microsoft done the same?

      Are you kidding? Sun has picked legal fights with IBM, Microsoft, Danger, Apache, and many more that have chosen not to come forward. Several companies I have worked for (no, not Microsoft) were threatened and badgered by Sun's lawyers over ridiculous intellectual property claims. When Java initially came out, there were some commercial third party implementations; Sun killed them. With Sun, there isn't a possibility of legal threats and killing third party implementation, Sun has a long history going back to day one.

      I don't know about who Microsoft has sued, but they have never sued or even threatened any company I have worked for (all competitors). Microsoft's misdeeds seem to be mainly related to bundling agreements and monopolization.

      You're not required to use the dead weight, I'm not seeing your point here.

      Oh, but unlike all other platforms, I am required to install and ship the dead weight. It says so right there in the license agreement.

      However, calling Java not-open and .NET more open is just Java bashing, pure and simple.

      Java deserves to be bashed, but that's not even the point here. I really don't care whether you use Java or COBOL or Forth. Hey, whatever floats your boat.

      I'm just using Java as a point of comparison. I'm saying that if something with so many legal, license, and patent issues hanging over it as Java is acceptable to open source developers, then people have absolutely no reason to complain about Mono.

    31. Re:what a troll by slack_justyb · · Score: 1

      I'm just using Java as a point of comparison. I'm saying that if something with so many legal, license, and patent issues hanging over it as Java is acceptable to open source developers, then people have absolutely no reason to complain about Mono.

      Well you could have saved us some time if that is all you are saying about this. I absolutely agree with that. There are issues with Java, just as there are with .NET and Mono and pretty much every other major computer advancement.

      That said, Mono bashers are indeed missing that no platform is without sin. OpenJDK offers a better choice for those seeking to wash their hands of Microsoft and worries that they might have of the company. Java, however, is not antibacterial soap to wash clean of everything that could happen legally.

      Quite incorrect. Both OpenGL and x86 have multiple independent implementations. Java does not.

      IBM J9 and GNU classpath don't count as independent implementations?

      Oh, but unlike all other platforms, I am required to install and ship the dead weight. It says so right there in the license agreement.

      Are you talking about Sun's Class Library? Then yes you are correct. Are you talking about other people's class library? Then you need to consult their license agreement. If they use the Java branding then they must accept the Sun specification for distribution to you, so long as you honor their agreement for their class library and forgo using Java branding or compatibility within your organization you are free to break up the class library as you see fit.

      I done this many times to fit the GNU class library when I'm limited on space. I obviously could not do this with the Sun class library since that is forbidden per the license agreement.

      Distribution of modified class libraries is pursuant to whatever agreement you got yourself in. The actual JVM is roughly about the same, basically, read the license you agreed to. If you want to implement your own JVM and/or class library, you are free to do so, so long as you either accept to be compliant with the Java standard as given by Sun or refrain from using the Java brand on distribution. This is exactly how Mesa works. Mesa is an open implementation of OpenGL but they can not use the OpenGL brand with distribution unless they agree to the license restrictions imposed by the Khronos Group, which runs counter to the GPL that Mesa is distributed under.

      Of course this is all just license agreements, this still does not protect you from infringement on core technologies that are patented. Of course, that's an incredibly larger issue. For example, Mono is looking to implement LINQ. LINQ is not within the ECMA .NET specification. Of course, Microsoft has agreements (not to sue promises) on technology that they add outside of the ECMA spec. At any rate that hasn't stopped people from making implementations of LINQ for other products (PHP, Java, and JavaScript). There is a big question as to what are the legal implications for implementing LINQ outside of an agreement with Microsoft. If they're smart they'll let it all pass; since in the end, it will only make more people develop with a Microsoft technology.

      Likewise, there is the same issue with some parts of Java. For example, JavaFX.

      Point remains is that the license for Java implementations outside of the Java-sphere (so to say) is that you can not claim jack squat about Java compatibility and you can not distribute as Java, if your implementation is outside the agreement for the Java trademark and brand copyright.

      Are you kidding? ... agreements and monopolization.

      No, are you kidding me? Yeah, Sun has come out swinging a lot. I'm not saying they are totally innocent. However, one of the core things is that J2EE be allowed to be implemented freely. It has been a big point of

    32. Re:what a troll by Anonymous Coward · · Score: 0

      I've not had the pleasure of being threaten by Sun or Microsoft. However, I do know who has been convicted of a software monopoly.

      Bill Gates may also eat babies for breakfast. What does that have to do with the legal and IP risks related to using a third party implementation of their platform?

      What matters is that Sun has a long history, nearly from day one, of using legal threats against companies and open source projects over Java, and this has had a negative effect on the availability of Java implementations. Microsoft hasn't done anything like that over .NET.

    33. Re:what a troll by 0xABADC0DA · · Score: 1

      In general, it is accepted wisdom that Java has 1) a better optimizing JIT; and 2) a more advanced GC. In practice, however, .NET often ends up being faster, simply because the languages and the platform itself offer more optimization opportunities.

      Java has a significantly better JIT and GC than CLR. Also CLR has actually significantly fewer optimization opportunities than JVM due to interaction of some of the features it has ('real' generics, value types, bytecode instructions). That's why the last known information has CLR only inlining one method at a time, if it doesn't cross assemblies, and isn't called through an interface, and it is less that 32 instructions long and contains no branches. Think about that. As inlining goes that's pathetically bad, and the reason is that the complexity explodes if they inline deeper. That precludes a whole host of optimizations.

      For example, .NET has value types, and standard class library uses them a lot - and they are obviously more efficient for specific cases. For Java to match this, it has to do escape analysis to determine where heap-allocated reference types are effectively used as if they were value types. Other examples include all methods in Java being virtual by default (whereas it's opt-in in .NET).

      Virtual methods are 'final' to the JVM until a class is loaded that overrides them. They have zero performance impact to a program. There's an interview with Andjers Heilsberg (lead language designer) where he doesn't even know this, so this is a common ignorance among C# developers. It also shows how absurd some of the design decisions were, that he cites performance as a reason for this.

      Value types can be faster, but this is a difference not an optimization. The reality is that value types (and the differences in the bytecode operations) cause an overall general slowness to CLR that affects everything. Then you throw in covariant+contravariant, generics, and other 'features' and you end up with a system that is prohibitively difficult to optimize. Value types are convenient for not having to manually write specialized classes, but that's the limit to their value. If you specialize the classes in Java you end up with better performance (but this is often not practical).

      Java does escape analysis because it can do it. For instance take this quote from one of the Sun developers working on invokedynamic implementation:

      One reason for this difference in approach is that the Microsoft CLR JIT does not appear to be under active development; its optimization level is as rudimentary as the earliest Java JITs. In the CLR that kind of performance is just the accepted cost of running managed code. ... While IronPython on the DLR has to do hard, brilliant work to "iron" out the wrinkles in the CLR JIT's weak performance profile, the "irony" is that Hotspot has already been optimizing highly dynamic programs for almost a decade.

      ... that's before invokedynamic.

      Language-wise, both platforms are doing pretty well. For comparison with your list, .NET has IronPython (which is in fact more up-to-date than Jython), IronRuby (which is still in alpha and generally less stable than JRuby), F#, and Boo.

      These pale in comparison to the languages that compile to JVM, in terms of performance, interoperability, and popularity.

    34. Re:what a troll by shutdown+-p+now · · Score: 1

      A serious question: why would real generics affect JIT performance? All I've seen of them was quite positive (i.e. they get optimized on a per-instantiation basis for value types, ditto for inlining etc - quite often I could get to essentially the same code as what a C++ compiler would do for STL).

      That's why the last known information has CLR only inlining one method at a time, if it doesn't cross assemblies, and isn't called through an interface, and it is less that 32 instructions long and contains no branches.

      Is this pre- or post- 3.5 SP1 release? There was a slew of improvements in the optimizer there, though I do not know all the details.

      Virtual methods are 'final' to the JVM until a class is loaded that overrides them. They have zero performance impact to a program. There's an interview with Andjers Heilsberg (lead language designer) where he doesn't even know this, so this is a common ignorance among C# developers. It also shows how absurd some of the design decisions were, that he cites performance as a reason for this.

      If you've read this interview, you know that the primary reason for that design was to avoid the brittle base class problem, and any performance benefits (perceived or real) are secondary to that.

      By the way, how does JVM deal with non-virtual methods suddenly becoming virtual when a new class gets loaded? The difference would be at call site, so does it mark all methods calling the one whose "virtualness" is affected for re-JITting on next call? Surely that does affect performance...

      Java does escape analysis because it can do it.

      Of course, there's nothing precluding escape analysis in CLR, either.

      These pale in comparison to the languages that compile to JVM, in terms of performance, interoperability, and popularity.

      Are you saying that Jython is more popular than IronPython? Do you have any reference to back this claim?

      In terms of performance, I vaguely recall seeing the numbers a long time ago, and they were mostly on the same level. But IronPython seems to be developing faster than Jython... in any case, again, do you have any references to back the claim, preferrably for current stable implementations?

      Interoperability - you've got to be kidding. One thing where .NET definitely beats the crap out of JVM, by design, is language interop. Wake me up when any version of Java will let me do dynamic invocation on Jython or JRuby objects (which is easily done in .NET 4 with either C# or VB). Or how about first-class tuples in all languages?

    35. Re:what a troll by Anonymous Coward · · Score: 0

      By the way, how does JVM deal with non-virtual methods suddenly becoming virtual when a new class gets loaded? The difference would be at call site, so does it mark all methods calling the one whose "virtualness" is affected for re-JITting on next call? Surely that does affect performance...

      Any code optimized to call that method as final is decompiled on loading a class that overrides the methods. This can be done for methods that are currently executing. This is practical because Java can efficiently interpret code, so not all code has to be JIT compiled so there is little time used recompiling methods while loading many classes.

      Are you saying that Jython is more popular than IronPython? Do you have any reference to back this claim? In terms of performance, I vaguely recall seeing the numbers a long time ago, and they were mostly on the same level. But IronPython seems to be developing faster than Jython...

      A new release 2.5 of Jython just came out 10 days ago. As far as I can tell IronPython is basically the only language actually used to a significant degree for CLR, whereas there are several for JVM.

      I don't know the current state of CLR optimizatoins, Microsoft does a good job of preventing public benchmarking, but I know that given the CLR features it's a safe bet that their optimizations are nowhere near Java's. It's just an intractable problem.

      Interoperability - you've got to be kidding. One thing where .NET definitely beats the crap out of JVM, by design, is language interop. Wake me up when any version of Java will let me do dynamic invocation on Jython or JRuby objects

      Invokedynamic now in jdk7. Regardless, you can call to Java objects and they can call back from all the existing languages on JVM; presumably they use reflection like the dynamic language runtime.

      Of course, there's nothing precluding escape analysis in CLR, either.

      Of course there is. To do escape analysis you have to analyze the code paths, usually between several methods. An object may never escape from a method with the parameters it's called with from a particular caller, but may escape with other parameters. So unless the analysis can be done on a large block of code it is unlikely to be of much help. Since Java can inline lots of methods into large blobs (because it can interpret to find hotspots) it can do escape analysis on these large blobs, considering all the paths that might be taken. C# cannot do this because (for reasons I mentioned before) it cannot really inline methods effectively.

      If you've read this interview, you know that the primary reason for that design was to avoid the brittle base class problem, and any performance benefits (perceived or real) are secondary to that.

      If you read the subtext, you see that performance is what was actually important. For instance, why no 'override' on extension methods? Instead they just don't get called. If they were really so concerned with correctness, why no design by contract?

      A serious question: why would real generics affect JIT performance? All I've seen of them was quite positive (i.e. they get optimized on a per-instantiation basis for value types, ditto for inlining etc - quite often I could get to essentially the same code as what a C++ compiler would do for STL).

      Suppose you have a List{Integer} and want to pass it to a method taking a List{Number}. In order to do this you need covariant typing or you need to construct a copy of the list. Constructing a copy may take a long time. And what if the method places a Number into the list... you can't just convert it back, and can't use a view without also doing a type check on inserts and whatnot.

      And with covariant typing, where List{Integer} inherits from

    36. Re:what a troll by shutdown+-p+now · · Score: 1

      As far as I can tell IronPython is basically the only language actually used to a significant degree for CLR

      Do you mean dynamic languages here? Because there are a lot of statically typed languages used on the CLR...

      Speaking of dynamic, there's JScript.NET, which is still quite often used as a scripting language of choice for .NET apps, despite being semi-deprecated (no updates since .NET 2.0, AFAIK). It was said that a replacement - "Managed JScript" - is in the works. There's also Scheme in form of Common Larceny. A bunch of other stuff, but mostly either abandoned or in alpha.

      If you read the subtext, you see that performance is what was actually important. For instance, why no 'override' on extension methods? Instead they just don't get called.

      Extension methods are a new (C# 3.0) language feature which appeared long after the original decision to have explicit virtual/override in the language, so I don't see how it's relevant. In fact, Anders probably carried explicit virtual/override from Delphi, which featured that prominently since the earliest versions.

      Anyway, the obvious reason why extension methods cannot override is because they are just syntactic sugar for static method invocations, and were never meant to be anything beyond that (which is why they didn't have to change the CLR for them).

      If they were really so concerned with correctness, why no design by contract?

      It's not about correctness, it's about versioning troubles. A lot of things in C# have to do with that (for example, the way it considers methods from base classes when doing overload resolution). Correctness is another thing entirely.

      As for DbC, it's actually coming in .NET 4.0, though as a library + IL rewriter solution for now, not at language level.

      Suppose you have a List{Integer} and want to pass it to a method taking a List{Number}. In order to do this you need covariant typing or you need to construct a copy of the list.

      Covariance is not an option here, since Liskov substition principle makes it very clear that List{Integer} cannot be used anywhere List{Number} is expected, precisely for the reasons you give later (because List{Number} can have Numbers added to it, while List{Integer} cannot). Allowing such covariance would be a hole in a type system, and no sane language would do that (it is, by the way, why Eiffel is not a sane language). Specifically, in .NET generics are invariant. They can be explicitly declared covariant or contravariant, but only where it is typesafe (and then no runtime checks are needed) - for example, IEnumerable{T} can be covariant, since T does not appear anywhere in parameter types of its methods (roughly speaking), but IList{T} cannot be. This is supported on CLR level in 2.0+, but not in the languages, and there are no generic variance annotations in the standard library - but all this stuff is coming in .NET 4.0.

      On top of that, real generics adds many new types, instead of there being one type per class there are any number of them.

      This isn't quite true. .NET JIT generates specialized instantiations of generic methods for different value types, but it does share quite a lot of code for reference types when it can(google System.__Canon for more details on that).

      A lot of JIT code in languages such as these works by inserting special cases for specific types and then using compares to see whether to execute that inlined branch or not.

      Well if there are many more types, this lessens the usefulness of doing these inlines (fewer of the objects will be of the exact same type as the inlined code was for).

      Erm, no. If a non-generic method inlines a generic one, it will inline a particular instantiation of it, so there are no comparisons there - e

  22. Try Gnote instead of Tomboy by Laven · · Score: 4, Informative

    Have you tried gnote yet? It is a C++ reimplementation of tomboy. gnote's binary package itself is less than 4MB with only a few standard dependencies that you might already have on a GNOME desktop, significantly smaller than Mono. I made the switch fully from tomboy to gnote a few months ago and things are working very nicely.

    1. Re:Try Gnote instead of Tomboy by ketilwaa · · Score: 1

      Last I read, Gnote doesn't have the same feature set as Tomboy, so that might have an impact on the size of the thing, although you're already comapring apples to oranges when you add in Tomboy deps with the install size. Also, the amount of disk space an app uses doesn't really tell you anything about how much other resources it actually uses. Some anecdotal evidence for the ricers out there: I have Tomboy running all of the time, and there is no difference in battery life with Tomboy running or not. That gives some idea that this is not a power sucking devil of an application it is made out to be.

    2. Re:Try Gnote instead of Tomboy by Anonymous Coward · · Score: 0

      Gnote is a nice port, but what about a port of F-Spot?

    3. Re:Try Gnote instead of Tomboy by Anonymous Coward · · Score: 1, Insightful

      Excuse me while I roffle a bit.

      Did you just compare tomboy + all dependencies + an additional 11MB made up from nowhere[0] to *just* the gnote binary? If you're going to spread misinformation, at least make it something that's not trivial to disprove.

      [0] http://www2.apebox.org/wordpress/rants/124/#comment-921

    4. Re:Try Gnote instead of Tomboy by Anonymous Coward · · Score: 0

      Yes , i am a gnote user, it works great :)

    5. Re:Try Gnote instead of Tomboy by nschubach · · Score: 1

      What do people use Tomboy for anyway? The only thing I've used it for is holding a URL when I rebooted (long story.) I used to just put that in a text file on my /home directory.

      I never opened it after that. I just don't get it's purpose besides digital post-its and even then it's kind of hard to administer them (ie: can't just drop in the trash... or can you?)

      --
      Every time I start to have faith in humanity, I ruin it by driving to work between 7 and 8 am.
    6. Re:Try Gnote instead of Tomboy by recoiledsnake · · Score: 1
      Gnote is not just a "re-implementation" of Tomboy, it's a line by line ripoff of Tomboy's C# code to C++ and GUI design. See http://robertmh.wordpress.com/2009/06/12/mono-in-the-default-install/for screenshots. And the developers of Tomboy are not happy.

      Our stance on Gnote is that it is counterproductive to maintain identical software in two languages. It will be harmful to the community, especially as these two apps inevitably diverge. It will result in duplication of effort, duplication of bugs, and a lot of wasted time for those who are trying to add value to the user experience. Tomboy is not going away, and it will continue to be developed on the extremely productive Mono/GTK# language platform. Anyone thinking about distributing Gnote should consider the impact on users and their data. When we develop, we should always be asking ourselves, "is this adding value for our users?"

      Also Tomboy does not have Applet support, which is why Debian wants it in the Gnome install instead of Gnote. From http://www.archivum.info/fedora-desktop-list@redhat.com/2009-04/msg00005.html :

      - We're using tomboy as an applet, which gnote currently does not support. I'm far from a notification area purist, but I do think that a note-taking application has no place in it... - If we are talking about replacing tomboy with gnote, we need to have some data migration that is more automatic that 'open terminal, cp .tomboy .gnote'. - While gnote on the surface looks like a clone of tomboy, if you look at the addins that come with tomboy, you'll probably find that gnote is not yet a full replacement for tomboy power users (it certainly works fine for my tomboy use...).

      You can use gnote if it fits your desires, but claiming that it should be default for ALL users is misguided. The Debian packagers know better than you.

      --
      This space for rent.
    7. Re:Try Gnote instead of Tomboy by Hatta · · Score: 1

      Why would I try gnote when Tomboy is already installed on my debian gnome desktop? Does gnote satisfy the tomboy dependency in apt? Or do I have to fix the dependencies myself?

      --
      Give me Classic Slashdot or give me death!
    8. Re:Try Gnote instead of Tomboy by Hatta · · Score: 2, Interesting

      Gnote is not just a "re-implementation" of Tomboy, it's a line by line ripoff of Tomboy's C# code to C++ and GUI design. See http://robertmh.wordpress.com/2009/06/12/mono-in-the-default-install/for screenshots. And the developers of Tomboy are not happy.

      If they didn't want people creating derivative works of their software, they shouldn't have released it as LGPL.

      --
      Give me Classic Slashdot or give me death!
    9. Re:Try Gnote instead of Tomboy by recoiledsnake · · Score: 1

      Gnote is not just a "re-implementation" of Tomboy, it's a line by line ripoff of Tomboy's C# code to C++ and GUI design. See http://robertmh.wordpress.com/2009/06/12/mono-in-the-default-install/for screenshots. And the developers of Tomboy are not happy.

      If they didn't want people creating derivative works of their software, they shouldn't have released it as LGPL.

      True, but lots of clones and forks do hurt a project.

      --
      This space for rent.
    10. Re:Try Gnote instead of Tomboy by robmv · · Score: 1

      Using GPL code on another GPL ported program (to another programming language) is a ripoff? and I am using Gnote 0.3.1 and it has Applet support, Gnote is being converted from C# to C++, and features and plugins are being ported one by one

    11. Re:Try Gnote instead of Tomboy by recoiledsnake · · Score: 2, Insightful

      Using GPL code on another GPL ported program (to another programming language) is a ripoff? and I am using Gnote 0.3.1 and it has Applet support, Gnote is being converted from C# to C++, and features and plugins are being ported one by one

      A line by line clone and completely identical GUI design to the pixel level and not respecting the developers wish can be called unethical even if it's legal under the GPL/LGPL. Most OSS developers won't mind some credit for their hard work. If Tomboy's developers do all the heavy lifting and Gnote just takes all of that and ports it line by line without adding any value except not having mono, that can be called a ripoff. Once Tomboy dies, Gnote might stagnate, because there is nothing more to ripoff and the single goal of Gnote(to remove Mono) has been achieved.

      --
      This space for rent.
    12. Re:Try Gnote instead of Tomboy by robmv · · Score: 2, Insightful

      A line by line clone and completely identical GUI design to the pixel level and not respecting the developers wish can be called unethical even if it's legal under the GPL/LGPL. Most OSS developers won't mind some credit for their hard work. If Tomboy's developers do all the heavy lifting and Gnote just takes all of that and ports it line by line without adding any value except not having mono, that can be called a ripoff. Once Tomboy dies, Gnote might stagnate, because there is nothing more to ripoff and the single goal of Gnote(to remove Mono) has been achieved.

      You and the authors may not like it, but that is the power of free software, I wanted to remove Mono from my system, Gnote is the response from someone that just wanted it too, they took the code and ported it, it could be a port to Java to run on Android, or to Javascript to be run on a palm Pre, it is a port, that not only allows me to run it the way I want, but give the opportunity to use that software on more architectures than Mono currently runs.

      I have seen the same kind of ports many times, for example porting Hibernate and Ant from Java to .Net and nobody called those ripoffs, someone needed the port, someone did it. get over it

    13. Re:Try Gnote instead of Tomboy by Anonymous Coward · · Score: 0

      Gnote is a nice port, but what about a port of F-Spot?

      Great idea, we'll call it G-spot and unveil it late this evening for you to play around with.

    14. Re:Try Gnote instead of Tomboy by Hatta · · Score: 1

      A line by line clone and completely identical GUI design to the pixel level and not respecting the developers wish can be called unethical even if it's legal under the GPL/LGPL.

      Whining like a little bitch when someone uses the software that you released for free is unethical.

      Most OSS developers won't mind some credit for their hard work. If Tomboy's developers do all the heavy lifting and Gnote just takes all of that and ports it line by line without adding any value except not having mono, that can be called a ripoff.

      Reducing bloat adds a considerable amount as far as I'm concerned. If the Tomboy developers want recognition for their work, they should write software that people actually want to use. If their choice of libraries is so objectionable that people would rather port it to other libraries than use their software, the fault isn't with the people making the ports, that's for sure. In other words, don't tell people what they want and expect appreciation. Give people what they want, and you'll get appreciation.

      Once Tomboy dies, Gnote might stagnate, because there is nothing more to ripoff and the single goal of Gnote(to remove Mono) has been achieved.

      If the project is worth continuing, those who care will continue developing. If no one is willing to keep the project alive, then it's no real loss. This is how open source works.

      --
      Give me Classic Slashdot or give me death!
    15. Re:Try Gnote instead of Tomboy by ultrabot · · Score: 1

      What do people use Tomboy for anyway? The only thing I've used it for is holding a URL when I rebooted (long story.)

      I use it take notes all the time - paste call stacks, breakpoint locations, bug reports, irc discussions.

      It doesn't do much (by design!), but it has a well designed ui that doesn't get in the way. I really recommend incorporating it or gnote to your workflow.

      --
      Save your wrists today - switch to Dvorak
    16. Re:Try Gnote instead of Tomboy by kelnos · · Score: 2, Insightful

      True, but lots of clones and forks do hurt a project.

      Too bad. Don't do things with your project that make too many people want to fork it, and you'll be fine. If a lot of forks appear, it just means you aren't fulfilling your users' needs. Which isn't even a bad thing! Forks are generally good, not bad.

      And in this case, your comment is a bit of a straw man -- as far as I can tell, Tomboy has one single fork/clone. Unless you're going to argue that *one* is "too many," I don't see how it's a problem...

      --
      Xfce: Lighter than some, heavier than others. Just right.
    17. Re:Try Gnote instead of Tomboy by Xtifr · · Score: 1

      A line by line clone and completely identical GUI design to the pixel level and not respecting the developers wish can be called unethical even if it's legal under the GPL/LGPL.

      Attempting to weasel a ginormous bloated ugly runtime created with very suspicious motives into one of the standard Linux desktops can be called unethical even if it's legal under the GPL/LGPL. My sympathies for the dickwads who are trying to shove Mono down my throat are precisely zero. I don't care what they do with their own software on their own systems on their own time, but when they try to slime their junk all over my desktop (and as a Debian developer who was involved with earlier stages of Gnome develoment, I have no hesitation about calling it "my desktop"), then they don't deserve to have their wishes respected, in my arrogant opinion. Screw 'em!

      Most OSS developers won't mind some credit for their hard work.

      So, give 'em credit for the UI design or whatever. Just keep their blankty-blank C# code off my freakin' system!

      Once Tomboy dies

      We can only hope.

      Gnote might stagnate

      If Gnote stagnates after Tomboy dies, then there probably wasn't enough there to sustain an actual project in the first place. Frankly, if it weren't for the underhanded plans to force the crappy C# runtime onto as many people's desktops as possible, I'm not sure Tomboy would exist in the first place, so you might be right, but I'd call that a good thing! If it can't justify itself on its own as a standalone application, then it has no business on my desktop no matter what runtime it uses.

      Just sign me a Debian Developer proudly using a mono-free Gnome desktop.

    18. Re:Try Gnote instead of Tomboy by tuomoks · · Score: 1

      Ok, enlighten me - is it like Sidekick from Borland a long, long time ago. That combined with Paradox, etc and with some other non-Borland tools / programs (relational databases, statistical tools, mail systems, Brief / some source / configuration control systems, too many to list..) were something I still can't find a replacement. Especially one which would run in a 8-12Mhz (not GHz) system with a couple of kilobytes of memory? In which I can chat, transfer files, etc on any network? Let it run on background, blah, blah, ..

      Seriously - Tomboy, MONO, whatever, we need those, not the fights. If they are overblown, protected by patents, whatever doesn't matter so much, we can always make another, or?

    19. Re:Try Gnote instead of Tomboy by ultrabot · · Score: 1

      Ok, enlighten me - is it like Sidekick from Borland a long, long time ago.

      Pretty much. OTOH, I never had much use for Sidekick back then because I was a kid that didn't do anything important enough to jot down ;-).

      --
      Save your wrists today - switch to Dvorak
  23. People are still on dial-up by tepples · · Score: 0

    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.

    Disk-hungry implies bandwidth-hungry. If you "find that a non-issue in general", you must not have friends or family who live in an area that doesn't have high-speed home Internet access.

    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.

    And when app maintainers do think up an original name, such as "Karbon14" or "Sodipodi" or "Amarok" or "Totem", they get bitched at for not coming up with a name that suggests to newbies what the program does.

  24. Re:Yessss by Aphoxema · · Score: 1

    I see some interesting points but nothing explains why the free software community can't make their own mono, why Microsoft still can't use this against F/OSS, or why we should stop arguing.

    It's more political bullshit...

    "Many of those who advertise themselves as anti-Mono are, quite frankly, frightening. Calling for the deaths of Microsoft employees (see comments on Boycott Novell), or trying to have people who make positive comments about Mono fired (see recent comments on Ubuntu mailing lists), or making insinuations about anyone who does not agree with them (see pretty much every news post on Boycott Novell itself) â" this is ugly behaviour, the absolute worst kind of advert for the âoeFree Software communityâ imaginable. If people want to be âoeagainstâ Mono, then there are sane ways to do it â" for example, by working on or packaging alternative software. Calling for people to be expelled from Free Software communities because they donâ(TM)t work on apps you like is, in short, the antithesis of supporting Freedom. If the anti-Mono crowd want to be taken seriously, then they need to UNDERSTAND what they fight against â" they need to have sufficiently intimate knowledge of what Mono is, how it works, and why, in order to know where to direct their energies (and general shouts of âoeZOMG! MICRO$HAFT!â isnâ(TM)t well-directed). I would LOVE to see some high-quality apps for GNOME written in, say, Java or Python â" as the competition would only result in better applications."

    Sounds like Republicans and Democrats fighting over how to tell people how to live their own damn lives. Just because I say Fuck Microsoft doesn't mean I'm a feral animal or that my words are a reflection of the Free Software community in general.

    The only Microsoft employee I'd be happy to see dead is Steve Ballmer, the rest I hope just have to find new jobs when Microsoft collapses into it's own greed and blind destructiveness.

    --
    "Most people, I think, don't even know what a rootkit is, so why should they care about it?"
  25. Estoppel by tepples · · Score: 1

    What's the proof? That Microsoft hasn't sued yet? That doesn't stop them from suing in the future.

    There is a "use it or lose it" doctrine at equity, called estoppel by acquiescence or laches. (And it's not just for trademarks.)

    1. Re:Estoppel by Anonymous Coward · · Score: 0

      How did that work out for TomTom? Oh. Yeah. . . they settled out of court so we don't really know if that defense would have worked out for patents or not. I suppose, though, that if they settled, it's because TomTom's lawyers didn't think they had a strong case.

      Still, you might be right - but I'd rather NOT get sued by Microsoft in the first place, which is why I removed Mono and Tomboy from my Ubuntu installation.

  26. that's irrelevant by jipn4 · · Score: 5, Interesting

    Even though Microsoft submitted the CLI and C# main components of .NET, MIcrosoft does hold at least one patent on the .NET infrastructure.

    First of all, they "don't hold a patent", they have filed a patent application. Whether that application gets granted remains to be seen, and even if it does, it's unclear what such a patent actually would cover or whether it could be enforced.

    Furthermore, even if the patent were valid and enforceable, it is irrelevant as far as Tomboy is concerned, since Tomboy and most other Mono desktop applications don't use the ".NET infrastructure", they use ECMA C# libraries and standard Linux libraries.

    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

    What's there to put in writing? You might as well demand Microsoft to put in writing that GNU C++, the Linux kernel, and Python are forever free from Microsoft royalties.

    1. Re:that's irrelevant by Anonymous Coward · · Score: 0

      Furthermore, even if the patent were valid and enforceable, it is irrelevant as far as Tomboy is concerned, since Tomboy and most other Mono desktop applications don't use the ".NET infrastructure", they use ECMA C# libraries and standard Linux libraries.

      I've seen tomboy use classes as XslTransform and XsltArgumentsList which are not part of the ECMA specification but are part of .NET framework.

    2. Re:that's irrelevant by setagllib · · Score: 1

      That's not even a bad idea, since they already published FUD about Linux' patent hygiene, putting the opposite in writing would finally put it to rest.

      --
      Sam ty sig.
  27. Re:Good by Anonymous Coward · · Score: 0

    Python is a fad language with hideous syntax. SciPy and NumPy libraries are -1 redundant. Why the hell would I want to code what Matlab or Maple can do right off the bat?

    PyFag: "Wow look at me I'm cool because I use python it allows me to leverage my synergies lolz!!!!11!!!!!"

  28. Red hat/Fedora improve, Debian/deb-based regress by Vexorian · · Score: 2, Insightful

    With Red hat/Fedora dropping Mono out of the gnome dependencies, and ubuntu and it seems even debian stick to their Mono ways. And ubuntu even threatening their users to install a lower quality Mono-dependent music player to replace Rhythmbox just because the Mono zealots are very, very loud about how they want to push this MS technology on everybody using free software. I guess I will have to change my current ways and just move to .rpm based Fedora. It's been a long time without red hat, shall be fun. "Let's all make gnome depend on MS technology just so we have a desktop widget that has already been ported to native code!" That's great...

    --

    Copyright infringement is "piracy" in the same way DRM is "consumer rape"
  29. Re:Yessss by wisty · · Score: 3, Interesting

    Yes, Mono probably has "patents" against it.

    So does every fricking application on the planet. 3D graphics? Patented. One click to buy? Patented. What's the bet that Microsoft has patents on half the Linux kernal?

    Can't they just do what every other free software project does, and just ignore the bloody things?

    Microsoft might sue, but they will probably just laugh. Nobody is going to re-implement the entire .net framework (including all the quirks of Microsoft's database layer, file system behavior, etc). Just look at the difficulties in getting data out of MySQL and PostGres in a sane way! Once you target a specific platform (i.e. the entire Microsoft stack) it's very hard to replicate.

  30. There are people still stuck on dial-up by tepples · · Score: 1, Troll

    20 minutes? I downloaded the source tarball in 10 seconds.

    Homes in rural areas of the United States[1] often can't get cable or DSL Internet. So a 10-second download would mean 40 KB, not the 6 MB of the current Tomboy 0.14.2 release found here.

    [1] The United States is home of Slashdot and Software in the Public Interest. People who live in rural areas grow the food that you eat.

    1. Re:There are people still stuck on dial-up by Freetardo+Jones · · Score: 1

      So if the yonly have a 4KB/sec download speed the size of a 6 meg package considering the entire time it will take to get the 700 meg debian ISO is going to be trivial.

    2. Re:There are people still stuck on dial-up by Anonymous Coward · · Score: 0

      [1] The United States is home of Slashdot and Software in the Public Interest. People who live in rural areas grow the food that you eat.

      Please, get those rural people back to work creating food and get them off our tubes.

    3. Re:There are people still stuck on dial-up by Anonymous Coward · · Score: 0

      That's ok, they only have to download it the once, given they all share a C64 with all their brother-aunts and assorted other "close" family.

    4. Re:There are people still stuck on dial-up by Anonymous Coward · · Score: 0

      People who live in rural areas will do what they are told. They will grow our food, or they will go destitute. Democracy forever!

      Are you seriously saying that we should work on reducing distributions to managable sizes for dialup connections?

    5. Re:There are people still stuck on dial-up by Anonymous Coward · · Score: 0

      You are actually trying to say that it is bad to include Tomboy (which is a bit more than "just a note taking application") because it adds 6 mb of download to your install that already has Gnome? (because this is added as a dependency to Gnome). If you have slow internet, just order the CDs. Really, saying that a general purpose distribution like Debian should not include some good free software because it is 6MB... There are special distributions that work for a small footprint already, why not use them?

    6. Re:There are people still stuck on dial-up by tepples · · Score: 1

      If you have slow internet, just order the CDs.

      That doesn't help when you get hit with 200 MB of updates between CDs.

  31. Re:Good by bluefoxlucid · · Score: 1

    You mean like Perl? or Ruby? TCL?

  32. Wrong. by John+Hasler · · Score: 2, Informative

    > Mono Squeezed Into Debian Default Installation

    It is not going into the Debian default installation. The Debian default installation does not include any "desktop environment". It is going into the Gnome "desktop".

    --
    Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
    1. Re:Wrong. by Anonymous Coward · · Score: 0

      It's going into the default Debian desktop install. Don't be a pedant.

    2. Re:Wrong. by Tetsujin · · Score: 1

      It's going into the default Debian desktop install. Don't be a pedant.

      You got to bear in mind, I think, that a lot of us may have been running Debian for ages, but may not have actually installed it in several years... I know that prior to last year (when I finally moved to AMD64) I had been on the same Debian install for ages... I don't think they had the "install profiles" back then, it was just "install base system" and then select the other stuff you wanted. Using dselect. :)

      --
      Bow-ties are cool.
    3. Re:Wrong. by Anonymous Coward · · Score: 0

      > Mono Squeezed Into Debian Default Installation

      It is not going into the Debian default installation. The Debian default installation does not include any "desktop environment". It is going into the Gnome "desktop".

      The Debian "default" installation is "Base" and "Desktop Environment" -- hence "GNOME" being the "default". ie; Those 2 tasks are selected "by default", you have to take action (read: change the default) to not install the "Desktop Environment".

  33. Re:Slow news day by moogsynth · · Score: 1

    So how many more years of them not suing anyone over Mono is it going to take before you people finally calm down and shut the fuck up? We've heard for 5 years this constant drumbeat that Microsoft is always around the corner waiting to sue people for Mono and none of you Chicken Littles have been right. Seriously, Microsoft deserves criticism for many things they have done in the past, but they have done right by this and have been about as open and willing to work with the FOSS community on Mono as one can really expect from a company like this.

    When Microsoft offer an unlimited patent covenant for all distributors of Linux software, people will stop complaining about it overnight.

  34. Microsoft's trojan horse into Open-Source? by Anonymous Coward · · Score: 0

    This debate seem to stem from a fear that this is Microsoft's trojan horse that's going to sneak it's way into open-source and blow it up with frivolous patent suits. Never mind that Microsoft has started licensing more and more programs (more) openly specifically to help the Mono platform. There are plenty of other problems with other vague patents granted in the US in use by open-source today. But they aren't getting as much attention.

    There are plenty of good arguments against bloat and the quality of the programs depending on Mono. But this patent rational isn't one.

    It's not even the entire framework that's affected by patents. Only a few parts. The worst that could happen would be that a few non-essential programs would have to be tweaked.

    Now, as I see it. This is Open-Source's trojan horse into a huge community of commercial .NET developers that are ever more embracing open-source software.

    Mono is the best way to let Windows developers transition into open-source environments.

  35. Re:Yessss by bluefoxlucid · · Score: 3, Insightful

    Legal departments are mostly "I'm scared Dave, will I dream?" They do anything that won't put them in an obviously worse position, just in case. Basically they're for negotiation and diplomacy; if Novell thinks Microsoft's claims on Mono are bullshit, they can call it, but Microsoft may raise something else real on them for happening to be uncooperative. If you are a ridiculous joke demanding money, they squash you; look at SCOX vs IBM vs Novell, with everyone else in the business world shelling cash to SCOX because they may have some legitimate claims, while IBM and Novell decided they were full of shit and not a real threat. You're too annoying and full of shit, IBM's going to stamp you into the ground.

  36. Re:Slow news day by Freetardo+Jones · · Score: 1

    When Microsoft offer an unlimited patent covenant for all distributors of Linux software, people will stop complaining about it overnight.

    Then maybe those other distros need to go talk to Microsoft and secure themselves a covenant like Novell did.

  37. Re:Slow news day by Jesus_666 · · Score: 1

    Just because they haven't been up to this specific case of scumbaggery doesn't mean they haven't been scumbagging the last couple years. They're scumbags; they keep demonstrating that. It's somewhat reasonable to expect further scumbaggery from them in the future.

    Plus, it took them ages to start suing over VFAT. That still didn't help TomTom. Any concerns over .NET/Mono may be unsubstantiated but we could only tell if we knew exactly how Microsoft is going to act over the next couple years. Since I'm not aware of any decent psychics in the F/OSS scene all we can do is make assumptions.
    You assume that sine they haven't sued anyone over Mono yet they won't do it in the future. I assume that since they habitually use morally questionable tactics they're likely to weaponize the .NET patents in the future. I have no idea who of us is going to end up being right so I err on the side of caution and stay away from .NET as a development platform and from Mono in general.

    --
    USE HOT GRITS WITH STATUE OF NATALIE PORTMAN (NAKED AND PETRIFIED)
  38. Re:Red hat/Fedora improve, Debian/deb-based regres by PhrkOnLsh · · Score: 1

    And ubuntu even threatening their users to install a lower quality Mono-dependent music player to replace Rhythmbox just because the Mono zealots are very, very loud about how they want to push this MS technology on everybody using free software.

    Almost as loud as the people opposed to "MS technology," developed before Microsoft had anything to do with Novell or any other GNU/Linux.

    I like bashing Microsoft as much as the next guy, but only when it's necessary. If anyone on /. actually kept up with the Debian blogosphere and Planet Debian, they'd see that there are two sides to every issue, and those sides aren't always political.

    http://www2.apebox.org/wordpress/?p=124 http://np237.livejournal.com/24065.html http://robertmh.wordpress.com/?p=12 "These are *APPLICATIONS* and forcing me to install them is, to my mind, antithetical to the open source ideal." "Evolution serves no useful purpose in today's world" Altogether, this whole argument just goes to show that users, even GNU/Linux users can be grossly uneducated on topics, hearing Microsoft, and jumping on the attack. We should mysteriously drop F-Spot and GnomeDo and Evolution and see how these morons react.

    --
    GNU/Linux: Freedom.
  39. As a .NET developer & a Linux user by BlueScreenOfTOM · · Score: 0, Redundant

    ...I'm very excited by this. I've been using Mono in Linux and OS X for a long time now and it has been working great. I'm not sure what Microsoft will think of this, but from what I've read thus far (which is admittedly not a ton) they haven't been getting in Mono's way... in fact, I believe that they gave information to help the Mono project so that it could be leveraged for Silverlight.

    Who knows what Microsoft is going to do in the future, but for now I'm excited for Mono.

  40. Incredible horrifying dial-up by tepples · · Score: 1

    but 50 MBs only takes 5-10 minutes on my pathetically slow DSL connection.

    In the country, 48 kbps dial-up is the norm, and 768 kbps DSL is blazing fast.

    But, you don't seem to get the idea of dependencies. To put it with a different language, you are complaining that a program coded in Java requires a Java VM to run

    If I am "complaining that a program coded in Java requires a Java VM to run", and I don't already have a Java VM, then I am complaining that the program was coded in Java in the first place.

    1. Re:Incredible horrifying dial-up by Limecron · · Score: 1

      Dialup is the norm? Satellite internet has been around for more than a decade and you can get 768k down for like $50/mo. Not significantly more than anyone would pay for cable or DSL.

      Sure, the latency is terrible, but it sure beats waiting days to download an update or a clip from YouTube.

  41. Re:Slow news day by moogsynth · · Score: 2, Informative
    No, that's a coppout. This is an example of a bad deal:

    Microsoft reserves the right to update (including discontinue) the foregoing covenant pursuant to the terms of the Patent Cooperation Agreement between Novell and Microsoft that was publicly announced on November 2, 2006; however, the covenant as set forth above will continue as to specific copies of Covered Products distributed by Novell for Revenue before such update.

    And this is an example of a good deal:

    Subject to the terms and conditions of this License, Google and its affiliates hereby grant to you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this License) patent license for patents necessarily infringed by implementation of this specification. If you institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the implementation of the specification constitutes direct or contributory patent infringement, then any patent licenses for the specification granted to you under this License shall terminate as of the date such litigation is filed.

    Non-disclosure agreements and time-limited covenants are by their very nature exclusive and are a complete joke to free software. If Microsoft really understood FOSS, they would have offered an agreement like that right off the bat.

  42. Re:Slow news day by Anonymous Coward · · Score: 0

    So how many more years of them not suing anyone over Mono is it going to take before you people finally calm down and shut the fuck up?

    If someone says it's going to snow in December this year, how many days of sunshine in July does it take to prove that the snow people are wrong?

    People are saying that Microsoft are going to sue once a significant number of Linux applications are dependent on Mono. Tomboy is not a significant number of applications. They would gain nothing by suing now. They will gain everything by suing once getting an injunction against Linux distributions including Mono means no Gnome and no KDE.

    You don't fire a cannon until your target is within range. Especially when you only have one cannonball.

  43. ISOs vs. updates by tepples · · Score: 1

    So if the yonly have a 4KB/sec download speed the size of a 6 meg package considering the entire time it will take to get the 700 meg debian ISO is going to be trivial.

    For people who use dial-up, ISOs are easy (CheapBytes, Ubuntu ShipIt, etc.), and updates are hard.

  44. awkward fact, may ruin exciting story by julian67 · · Score: 4, Informative

    http://svn.debian.org/viewsvn/pkg-gnome/desktop/unstable/meta-gnome2/debian/control?revision=20303&view=markup

    "Depends: gnome-desktop-environment (= ${source:Version}),
                      gdm-themes,
                      gnome-themes-extras,
                      gnome-games (>= 1:2.24.3),
                      libpam-gnome-keyring (>= 2.24.1),
                      gstreamer0.10-plugins-ugly (>= 0.10.10),
                      gstreamer0.10-ffmpeg (>= 0.10.6),
                      rhythmbox (>= 0.12),
                      synaptic (>= 0.62),
                      system-config-printer (>= 1.0.0),
                      totem-mozilla,
                      swfdec-mozilla,
                      epiphany-extensions,
                      gedit-plugins,
                      evolution-plugins (>= 2.24.3),
                      evolution-exchange (>= 2.24.3),
                      evolution-webcal (>= 2.24.0),
                      serpentine,
                      gnome-app-install,
                      transmission-gtk,
                      bluez-gnome,
                      arj,
                      avahi-daemon,
                      tomboy (>= 0.12.2) | gnote,"

    note: tomboy (>= 0.12.2) | gnote

    In plain English that means tomboy *or* gnote.

    It's Debian, you have a choice.

    Debian also offers an Xfce/LXDE version of CD1 and a KDE version of CD1, CD1 being the installer. Neither of these offer mono or Gnome (duh!). Debian also offers fine grained package selection in all the installers, and a netinstall and a tiny netinstall, the businesscard iso. There is also the DVD installer which offers a choice of desktop environments along with the usual options for fine grained selection of packages, the 'Expert Install' option.

    So *one* of the numerous ways of installing Debian *may* offer Tomboy to those who want it. Cue howls of intolerant, ill-informed, unsubstantiated quasi-religious outrage.....

    And anyway mono is accepted as free software by the two bodies which are best placed to determine its status, the FSF and the OSI (and Debian Legal as well). Their legal teams have somehow failed to persuaded by psychotic ravings and are obstinately insistent in assessing these things by means of reason, facts, law and other little know methods. How churlish.

    On the other hand it might be a far reaching conspiracy and have something to do with the Kennedy assassination, 9/11 and Roswell.

    1. Re:awkward fact, may ruin exciting story by Late+Adopter · · Score: 1

      My understanding of the situation is that Tomboy is in the "recommended" position of the two, that is, if you install Gnome and specify nothing else, Tomboy will get installed, along with Mono, instead of GNote.

      That seems like a silly choice considering Tomboy+Mono is a larger size and runs on fewer architectures. I would've gone with GNote to at the very least save space on the install CD, and then let people who know they want it install Tomboy from the repositories.

    2. Re:awkward fact, may ruin exciting story by julian67 · · Score: 1

      Maybe that will happen. It's just as likely as anything else. This is in Sid. There are at least 18 months until a new Debian release. Sid now does not translate into Debian stable 2011. Sid's a big mish mash, there's no assurance that anything in there now progresses to stable or anything not in it right now won't run that course. Sid's not even guaranteed to be complete in itself. It may have missing or broken libraries and dependencies.

      It's a development branch. Stuff changes every day of every week.

      The people getting self-righteously outraged about some (free software) packages in a development branch, Sid, or writing headlines about 'the default install' aren't doing much more than reminding everyone that they are remarkably stupid as well as loud and tiresome.

    3. Re:awkward fact, may ruin exciting story by Anonymous Coward · · Score: 0

      You have lost this argument.

      Simply because you are unnecessarily acting like an arsehole to lots of people.

      If you have nothing civil to say. Shut up.
      Mod me troll if you wish, but I've seen the same behaviour on slashdot, the debian bug, and both parties blogs.

      I'd never heard about either party prior to this slashdot story, and now I'd wish I'd never heard of one of the parties.

    4. Re:awkward fact, may ruin exciting story by julian67 · · Score: 0, Troll

      "you are unnecessarily acting like an arsehole... "

      "If you have nothing civil to say. Shut up."

      There speaks the voice of reason, a mellow tone, enhanced by the author's keen grasp of facts, generous nature and delightful delicacy of writing style. Conoisseurs of English, philosophy, manners and other of the gentle arts please gather and drink deeply of this wisdom. Be thankful that the muse has blessed us all.

    5. Re:awkward fact, may ruin exciting story by Anonymous Coward · · Score: 0

      It's Debian, you have a choice.

      How cute, they think that's a choice.

      Sincerely, A Smug Gentoo User

    6. Re:awkward fact, may ruin exciting story by Anonymous Coward · · Score: 0

      I think the problem is, more or less, mental.

      Let's put it this way: Because, as you see, FOSS projects must rely on Microsoft's innovation, so FOSS must be inferior to proprietary software (in general, and Microsoft in particular). Plus, if they rely Microsoft's innovation here, who knows if they steal other innovations somewhere else?

      Sure, it is a choice, but why bother? Why not just give the user a purely free installation, after which they can (easily) install Microsoft-innovation should they so choose? Oh, I get it, it is because Debian project must be so afraid that the Free solution is not good enough, so they must provide back up (aka Microsoft technology)! See, FOSS is but a joke. Proprietary is the only way to go. Oh, maybe because installing new software in Debian must be very difficult, which involves in stealing more software, compiling drivers from scratch, and eating children. That's right, that's why Mono is needed.

      To tell you the truth, I don't really care if Ubuntu includes Mono by default (because I default that distro to be broken anyway), but for Debian, one of the most important distro of GNU/Linux, to do this, well, I have not words to express my disappointment in the matter.

    7. Re:awkward fact, may ruin exciting story by julian67 · · Score: 2, Interesting

      Free software relies on all kinds of sources. The GNU system itself was/is a re-implementation of UNIX. Many of the languages used started off as proprietary. There's nothing new in this. Where is the campaign to purge Fortran or Pascal from the free software opus? Why no campaign against Samba and the use of the SMB protocol? Why is nobody outraged at DotGNU? Where are the calls to cease supporting .avi container and other MS developments?

      Essentially this hatred of mono is about its origin not its qualities or legal status. That is Microsoft in the first instance and then it's a continuation of long standing and often vitriolic personal attacks on M de Icaza which gained added impetus and some spice with Novell's deal with MS.

      It's hard to debate with people when their fundamental position is composed essentially of hatred, fear and dislike of persons or groups. Where is the factual basis? Where is the ability to consider anything useful when hate or fear is the driving force? This is religion by another name, it cannot be reasoned with, it is impervious to contradictory verifiable fact, it allows no deviation.

      I find it curious that one of the people who might agree quite strongly with the botycottnovell stance is a certain Mr S. Ballmer. He's known to have a similar affable nature and often makes the startlingly similar assertions regarding patents and free software.

      boycottnovell couldn't be doing a better job if they were a paid Microsoft stooge.....

    8. Re:awkward fact, may ruin exciting story by Ansoni-San · · Score: 1

      Well if you kill Tomboy there'll be no Gnote. So it makes no sense to consider Gnote an alternative to Tomboy.

      All that Tomboy and Gnote users will be left with are these developers which have clearly demonstrated their lack of software design skills, leadership, or vision. Which indeed hurts everyone because it means one less high quality Unix/Linux desktop app.

    9. Re:awkward fact, may ruin exciting story by Lorien_the_first_one · · Score: 1

      Well, you have a good point there...

      --
      The diversity and expression of human opinion is essential to human survival.
    10. Re:awkward fact, may ruin exciting story by bachnit37 · · Score: 1

      Dugg for mentioning Roswell. Oh wait, where am I???

    11. Re:awkward fact, may ruin exciting story by VoltageX · · Score: 1

      There's also a BluRay ISO for the truly insane.

      --
      "Anonymous could not immediately be reached for further comment." - International Business Times
  45. Re:Yessss by ketilwaa · · Score: 3, Informative

    Stallman did comment on Mono, and it's not necessarily what one would expect: See?

  46. Someone please correct me if I'm wrong by overshoot · · Score: 2, Interesting
    But wasn't the GNOME project founded because KDE depends on Qt, which is not adequately "free?"

    If that's true, could someone explain to me how MS.NET is "more free" than Qt?

    --
    Lacking <sarcasm> tags, /. substitutes moderation as "Troll."
    1. Re:Someone please correct me if I'm wrong by pak9rabid · · Score: 1

      But wasn't the GNOME project founded because KDE depends on Qt, which is not adequately "free?"

      Historically yes, but that's no longer the case.

      If that's true, could someone explain to me how MS.NET is "more free" than Qt?

      I agree whole-heartedly. It's shit like this that will push the FOSS loyalists away from GNOME and to other window/desktop managers. KDE4 is becoming a very attractive option as it becomes more mature.

    2. Re:Someone please correct me if I'm wrong by lastman71 · · Score: 1

      1) Tomboy don't require MS.net at all.
      2) Mono is gpl, while qt was not. Qt had a commercial license that was free (no pay required) only for linux. You had to pay for every other OS.

      So the question is quite misleading.

    3. Re:Someone please correct me if I'm wrong by Anonymous Coward · · Score: 0

      Until recently, Qt wasn't licensed under a license that the FSF considered 'open', because it had certain clauses that restricted commercial usage, IIRC. Mono is actually open. The only reason that people are claiming that Mono somehow isn't free is because there's a slim possibility of Microsoft being able to say that it's infringing on a patent. The actual license is accepted by the FSF.

      IMO, the chances of Microsoft killing Mono are less than them doing it to Linux in general. Microsoft wants Mono around, since it means that apps written for linux, in mono, can work on Windows too. People need to realize that companies like MS aren't motivated by 'hate' towards OSS, they do what's in the best interests of their bottom line.

    4. Re:Someone please correct me if I'm wrong by gbjbaanb · · Score: 1

      your answer is misleading, who care about how things *were*. What is the state of play today, and possibly consider the state of thing to come.

    5. Re:Someone please correct me if I'm wrong by Vahokif · · Score: 0

      GNOME was started by the same guy who started Mono (Miguel de Icaza).

    6. Re:Someone please correct me if I'm wrong by jmorris42 · · Score: 1

      > But wasn't the GNOME project founded because KDE depends on Qt, which is not adequately "free?"

      Sorta. Qt was totally not free when KDE began, it was only a 'free download, but only for the Linux version' sort of free. The same sort of ferret coders who couldn't get past "Qt shiny, me want!" are the sort who now want to handwave away all criticism of the non-code legal/political issues surrounding Mono. Back then enough people saw the danger of basing the entire Free Software desktop effort on a small commercial software house's unfree code that GNOME was founded in response. It is almost certainly a direct response to that pressure that eventually caused Qt to now be 100% Free.

      No such response is required to Mono, only keeping it at arm's length. If we never allow it to become a standard part of our software base and build no major hard to replace flagship applications upon it the odds are Microsoft will never launch an attack.

      Of course if we do this the critics will always insist we were fools to not avail ourselves of the incredible Microsoft technology and that we held back progress. But expenditures on defenses are always like that, it is hard to count the cost of the wars not fought while the ships, planes and tanks have measurable costs. Thus it is here, if Microsoft never attacks we will never know what costs we saved, but the odds of having the patent armegeddon are greatly increased if we lower our guard and make ourselves a target they can't refuse striking.

      --
      Democrat delenda est
    7. Re:Someone please correct me if I'm wrong by Anonymous Coward · · Score: 0

      May it have something that the qt libraries was free , but they where under gpl which meant any app linking into it had to be opensource,
      i like opensource , but i wouldnt use it for the world if it enforced me to be opensource , think about any commercial app if libc was licensed the same way,
      which for me atleast since i actually develop for the food on my table , i selected gtk at that time even tough qt is better and more cool stuff , i wanted a
      toolkit which i could use for any project , not just my hobby projects.

      Qt is now lgpl so its very nice , but the reason for the switch was because of gpl on a library. it was a insane thing on qt's part and actually( even stallmann agrees , and thats
      why the lgpl was born ) they lost alot of revenue on this clause and messed up the community. think its a bit to late , im sure had there been a lgpl clause on qt from the start
      it would have been the prime cross platform gui toolkit out there. almost on level with the boost lib which is the defacto c++ utility library.

      if your not a developer i can see the , whats the deal , gpl is all the same , well its not.

      If you make your project gpl(without the L infront) , anyone who uses the code has to release theyr code , which is a fair imo ,
        but with a library gpl licensed ( not lgpl it doesnt care , it just want that if you modify the library you have to post the code ) , you would be enforced to release your code for a totally separate app for just using what many would say is standard programming libs on a platform., thats why no libs is licensed as gpl except dual licensed shit where you have 2 versions , one where you are free to use in any app and you pay $9999 for the lib and one that is free that can only be used for "gpl" software , its a typical vendor locking scenario if you start to use it.

      ooh and you say , well adobe f.ex should pay for it , they can afford it .. well take this scenario , i work as a developer consultant and cant really compete when i make a custom app for a client which noone outside ever cares about , the client will get all the source ofc , but when i tell them they have to pay $9999 since they dont wanna share theyr company secrets i am in big trouble , and for real why would i choose a lib like that when it doesnt cost me more than 30 mins to use a free to use for whatever you like lib.

      anyways thats a thing of the past , but trollteck created this shit and tbh i hope they die since they are the ones who destroyed the linux desktop forever. but ofc kudos for them creating a excellent lib., but still i hope they burn.

    8. Re:Someone please correct me if I'm wrong by Draek · · Score: 1

      The state of play today: QT is Free, Gnome aims for a different purpose than just being a KDE substitute, Mono is still GPL, and Tomboy still doesn't require MS.NET.

      The state of things to come: QT sure to continue being Free, Gnome likely continuing to aim at its particular niche, Mono almost certain to continue being GPL, and Tomboy almost surely continuing to run without needing MS.NET.

      Your point?

      --
      No problem is insoluble in all conceivable circumstances.
    9. Re:Someone please correct me if I'm wrong by Draek · · Score: 1

      If we never allow it to become a standard part of our software base and build no major hard to replace flagship applications upon it the odds are Microsoft will never launch an attack.

      Chances are, if we *do* allow it to become a standard part of our software base and build major hard to replace flagship applications upon it, Microsoft will *still* never launch an attack. Patent-based FUD is an incredibly ineffective form of "warfare", as the Linux incident proved a while back, not to mention very limited geographically speaking.

      But I hope you're using NetBSD, you know, in case Microsoft *does* have patents over the Linux kernel. Just think of the potential costs.

      --
      No problem is insoluble in all conceivable circumstances.
    10. Re:Someone please correct me if I'm wrong by Zott+and+Brock · · Score: 1

      And this is probably the real reason why the Gnome people are pushing Mono.

    11. Re:Someone please correct me if I'm wrong by Anonymous Coward · · Score: 0

      GNOME was created because KDE depends on Qt which in that time wasn't free software. Later to now Qt is free open source software licenced under 3 licences (qt licence, GPL v.2 and GPL v.3) ... Hava a look at

      http://en.wikipedia.org/wiki/Qt_(toolkit)

      I cannot see MS.NET even being free...

  47. OpenOffice.org as well! by Anonymous Coward · · Score: 0

    From bjorn.haxx.se (please think of the slashdot effect). I found this surprising.

    captcha: arrogant

    1. Re:OpenOffice.org as well! by petermgreen · · Score: 1

      note that testing migration is handled based on source packages. So if any binary package generated from the openoffice.org source package depends on mono it will be considered a dependency for testing migration purposes.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
  48. Re:Red hat/Fedora improve, Debian/deb-based regres by PhrkOnLsh · · Score: 1

    (/. mangled my last paragraph)
    http://www2.apebox.org/wordpress/?p=124 irrational?
    http://np237.livejournal.com/24065.html zealots?
    http://robertmh.wordpress.com/?p=12 hm, this whole argument was blown out of proportion by the GNOTES DEVELOPER. Sounds more like a whiny developer pissed that his package wasn't included rather than a real issue.
    "These are *APPLICATIONS* and forcing me to install them is, to my mind, antithetical to the open source ideal." No one is forcing you to install anything. Every reasonably competant debian user knows NOT TO INSTALL THE METAPACKAGES! Anyone else should run Ubuntu.
    "Evolution serves no useful purpose in today's world" huh? Right, so the only thing that is going to ever get GNU/Linux accepted as a replacement for MS Windows in corporate settings is useless?
    "It's just like Wine and DOSEmu: a gateway to viruses that originated on Microsoft platforms." ...what? It's not a fucking interpreter or an emulator, it's a compiler for Christ's sake! Read your fucking code before you compile it if you're that scared of the "M$ BOOGY MONSTER."
    Altogether, this whole argument just goes to show that users, even GNU/Linux users can be grossly uneducated on topics, hearing Microsoft, and jumping on the attack. We should mysteriously drop F-Spot and GnomeDo and Evolution and see how these morons react.

    --
    GNU/Linux: Freedom.
  49. zim by Anonymous Coward · · Score: 0

    I love zim:

    Zim - A Desktop Wiki
    http://zim-wiki.org/

  50. Trolls calling trolls trolls. New low on Slashdot. by Hurricane78 · · Score: 1

    How exactly is this article trollish?
    To me, this whole discussion sounds like the "monkey see, monkey do" problem. Most people do not even know why they think that the other side trolls.

    I mean, it sounds like a good point and an even likely thing, that Microsoft is going to sue and try to forbid Gnome, because they in fact have patents on .NET.
    We remember how SCO happened, and the general EEE policy that killed or nearly killed Sun, Netscape, Borland etc.
    We also remember that all of them had some kind of contract, controlling what is ok, and what is not ok. and Microsoft perfectly worked their way around it.

    I also find is most funny, that the whole point that started Gnome, was that KDE was not entirely free, and Trolltech could sue. ^^ (Which now seems fixed, by the way.)

    I am not taking any sides here. I am just using basic logic, and likeliness calculated from my experience.
    Please enlighten me. But first think about the why, and stay with the facts (past and present), instead of being part of a lynch mob.

    (Luckily, I use KDE, because it actually leaves the freedom of choice to the user. So I'm out anyway.)

    --
    Any sufficiently advanced intelligence is indistinguishable from stupidity.
  51. Some appear to have short memories by Anonymous Coward · · Score: 0

    I can still remember the whining by the GNOME fanboys about KDE using that evil, proprietary Qt product. Remember how Trolltech was either going to clamp down and eventually destroy KDE, or worse yet fold up and leave them with unmaintainable code?
    So now the GNOMEsters have taken the candy and are getting in the car with the serial corporate criminal and convicted monopolist.

  52. Re:Mono is a gateway to cross-platform virii by Anonymous Coward · · Score: 0

    Objective C beats C# like Chris Brown beats Rihanna.

  53. Josselin Mouette is not Debian, he's just a jerk by Anonymous Coward · · Score: 0

    Josselin Mouette does not speak for nor set policy for Debian. He's just a pushy immature unmannered jerk who managed to slip something in early in the development cycle. There's no way this is going to survive until the Squeeze release.

    Read the bug reports, do a web search on his name. Read about his past censures by Debian's self-correcting policy infrastructure.

    If there is one thing Debian is good at, it's a strong policy with strict procedural discipline. It's not about to go all mushy over a minor note-taking applette pushed in by a devel with very poor standing in the community. (did I mention what a jerk he is?)

    Especially when Gnote is a near-identical clone to Tomboy, and it's not like this is a core feature.

  54. Re:Mono is a gateway to cross-platform virii by ericrost · · Score: 0, Offtopic

    AFFECT, something affects something else. The way in which it affects it often leads to effects.

  55. Re:Good by Anonymous Coward · · Score: 0

    Python is a turd. I don't know why it's so popular on slashdot. Oh, wait I do know. It's designed for idiots. Just like VB. Or PHP. Look through the Python FAQ sometime. "Why do you ...", "Why don't you ..." -- the answer is always the same: you're too stupid.

  56. Re:Mono is a gateway to cross-platform virii by recoiledsnake · · Score: 1

    Wrong:
    Appeal of C# over Objective-C:
    C# code is less repetitive than Objective-C code
    No need to declare every IB plug 4 times, only once.
    Runs in a safe VM
    No buffer-overflows
    No crashes due to uninitialized memory
    No dangling pointers
    Garbage collection for all types
    Lambda expressions (great for GUI programming)
    Iterators
    Generic programming for type safe coding.
    Type inferencing for reduced typing.
    Dynamic code generation
    IronPython talks to C# objects naturally (out of the box)
    Superior XML libraries
    LINQ to XML, LINQ to Objects, and maybe some day LINQ to Databases.

    --
    This space for rent.
  57. Real man note taking... by lotho+brandybuck · · Score: 1
    1. Open terminal.

    2. cat > /dev/null

    3. type notes.

    Just don't close the terminal window.

  58. 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.
    1. Re:FUD by uberjack · · Score: 0, Flamebait

      Speaking of which, isn't Rhythmbox the audio player of choice for GNOME ? And given that, doesn't pretty much every Linux distro now come with Mono preinstalled? IIRC, Evolution is Mono-based as well, Evolution being GNOME's mail program of choice.

    2. Re:FUD by Tom9729 · · Score: 1

      Rhythmbox is written in C. Perhaps you're thinking of Banshee?

      I don't know what Evolution is written in, but unless they rewrote the whole thing in the past few years (something I very much doubt) it is not Mono/C#.

    3. Re:FUD by Tom9729 · · Score: 3, Informative

      Mono itself has been in the Debian repos for a pretty long time and really isn't the issue here.

      This particular "spat" is because Debian is making Mono a dependency of Gnome, with the only justification being that Tomboy (a post-it note application) requires it, which many people see as unnecessary.

    4. Re:FUD by stinerman · · Score: 1

      Not to mention...what constitutes a "default" install of Debian? Perhaps I always install in expert mode, but I wasn't aware that there was a default other than the essential programs like the kernel, framebuffer, bash, etc.

    5. Re:FUD by gd2shoe · · Score: 1

      They might mean "Desktop environment" in tasksel (a standard step during installation).

      --
      I won't join Slashcott. OTOH, If Beta goes live, I just won't be back until it's fixed. Sorry Dice.
    6. Re:FUD by petermgreen · · Score: 1

      The default is to install the base system (the really important stuff) standard system task (a load of old unixy stuff). Depending on the language you select some language specific stuff will be installed and if you are on a laptop some power management related stuff.

      TFA is titled "default desktop install" which probablly reffers to the above plus selecting teh "desktop environment" task when the installer brings up tasksel. IIRC that will (among other things) drag in the gnome metapackage and anything it depends on.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    7. Re:FUD by LizardKing · · Score: 2, Insightful

      Evolution is written in C. It's another of Miguel's "abandoned" projects, as the man seems to be pathologically incapable of working on something until it's mature (see Gnumeric, the Bonobo component system for GNOME, Evolution).

    8. Re:FUD by jroysdon · · Score: 1

      No mono/C+ in evolution, but there is in tomboy.

      $ cat /etc/redhat-release
      Fedora release 11 (Leonidas)
      $ yum deplist evolution
      Loaded plugins: refresh-packagekit
      Finding dependencies:
      package: evolution.i586 2.26.2-1.fc11
      dependency: libatk-1.0.so.0
      provider: atk.i586 1.25.2-2.fc11
      dependency: libgio-2.0.so.0
      provider: glib2.i586 2.20.1-1.fc11
      dependency: libessmime.so.0
      provider: evolution.i586 2.26.1-2.fc11
      provider: evolution.i586 2.26.2-1.fc11
      dependency: libsmime3.so(NSS_3.4)
      provider: nss.i586 3.12.3-4.fc11
      dependency: libglib-2.0.so.0
      provider: glib2.i586 2.20.1-1.fc11
      dependency: libetimezonedialog.so.0
      provider: evolution.i586 2.26.1-2.fc11
      provider: evolution.i586 2.26.2-1.fc11
      dependency: libplc4.so
      provider: nspr.i586 4.7.3-5.fc11
      dependency: libICE.so.6
      provider: libICE.i586 1.0.4-7.fc11
      dependency: libart_lgpl_2.so.2
      provider: libart_lgpl.i586 2.3.20-4.fc11
      dependency: libedataserverui-1.2.so.8
      provider: evolution-data-server.i586 2.26.1-1.fc11
      provider: evolution-data-server.i586 2.26.2-1.fc11
      dependency: libnsl.so.1
      provider: glibc.i586 2.10.1-2
      provider: glibc.i686 2.10.1-2
      dependency: libgweather.so.1
      provider: libgweather.i586 2.26.1-1.fc11
      dependency: gnome-themes
      provider: gnome-themes.noarch 2.26.1-1.fc11
      dependency: libegroupwise-1.2.so.13
      provider: evolution-data-server.i586 2.26.1-1.fc11
      provider: evolution-data-server.i586 2.26.2-1.fc11
      dependency: libc.so.6(GLIBC_2.2)
      provider: glibc.i586 2.10.1-2
      provider: glibc.i686 2.10.1-2
      dependency: libnss3.so(NSS_3.3)
      provider: nss.i586 3.12.3-4.fc11
      dependency: libicalvcal.so.0
      provider: libical.i586 0.43-4.fc11
      dependency: libdl.so.2
      provider: glibc.i586 2.10.1-2
      provider: glibc.i686 2.10.1-2
      dependency: libexchange-storage-1.2.so.3
      provider: evolution-data-server.i586 2.26.1-1.fc11
      provider: evolution-data-server.i586 2.26.2-1.fc11
      dependency: libgdata-google-1.2.so.1
      provider: evolution-data-server.i586 2.26.1-1.fc11
      provider: evolution-data-server.i586 2.26.2-1.fc11
      dependency: libpango-1.0.so.0
      provider: pango.i586 1.24.1-1.fc11
      dependency: libfilter.so.0
      provider: evolution.i586 2.26.1-2.fc11
      provider: evolution.i586 2.26.2-1.fc11
      dependency: libgmodule-2.0.so.0
      provider: glib2.i586 2.20.1-1.fc11
      dependency: libpthread.so.0(GLIBC_2.3.2)
      provider: glibc.i586 2.10.1-2
      provider: glibc.i686 2.10.1-2
      dependency: libX11.so.6
      provider: libX11.i586 1.2-3.fc11
      dependency: libc.so.6
      provider: glibc.i586 2.10.1-2
      provider: glibc.i686 2.10.1-2
      dependency: libedataserver-1.2.so.11
      provider: evolution-data-server.i586 2.26.1-1.fc11
      provider: evolution-data-serve

    9. Re:FUD by nicolas.kassis · · Score: 2, Insightful

      Don't knock him down for that, the guy is a hacker and he won't keep working on something if it becomes mundane and boring. I can understand that he likes to move on to new problems and work on them.

    10. Re:FUD by jroysdon · · Score: 1

      Doh, scratch the C+ part, meant C#.

    11. Re:FUD by Aphoxema · · Score: 1

      This particular outburst of concern is FUD.

      How ironic.

      --
      "Most people, I think, don't even know what a rootkit is, so why should they care about it?"
    12. Re:FUD by Aphoxema · · Score: 1

      Post-It notes are inefficient pieces of trash-to-be only the passive-aggressive are equipped to handle effectively.

      Their occurrence in a business environment is a sign of organization to management, but to an... insightful observer they are a reflection of erroneous thinking that labels can replace structure and concentrated effort.

      Let's review the evolution of Post-it notes:

      Ideas > Information > Words > Writing > Paper > Notepads > Post-It notes > Tomboy > Twitter

      Mind that those are "greater-than", not just arrows.

      --
      "Most people, I think, don't even know what a rootkit is, so why should they care about it?"
    13. Re:FUD by atraintocry · · Score: 1

      Sometimes I write something on a post-it note when I want to remember it later. I do this because they are made of paper.

    14. Re:FUD by Aphoxema · · Score: 1

      Sometimes I use pieces of paper that don't have glue on the back of them that can fit more than

      "feed cat food
      at 3:00"

      But I usually choose to practice my innate ability to remember to do things without a piece of paper, which I would also probably forget to look at when the time comes.

      --
      "Most people, I think, don't even know what a rootkit is, so why should they care about it?"
    15. Re:FUD by K.+S.+Kyosuke · · Score: 1

      the man seems to be pathologically incapable of working on something until it's mature

      I think the word you are looking for is "startup founder".

      --
      Ezekiel 23:20
    16. Re:FUD by Rutulian · · Score: 1

      You are correct. The only official Gnome application that uses Mono is Tomboy. There are no core dependencies on Mono.

    17. Re:FUD by Daengbo · · Score: 1

      Last I checked, Tomboy was installed for Lenny when you chose Gnome in Aptitude (because it was recommended, but not a dep). This argument should have occurred back then if at all.

    18. Re:FUD by itomato · · Score: 1

      There are 16 different takes, with equal measures of outburst.

      The big deal is that one stinkin' utility application on the desktop requires the inclusion of ~50MB of what some people consider to be 'tainted' libraries.

      A notepad, for which there is already a replacement.

      The issue is that 'GNOME 3 Mono', and if you want one, you're getting the other, with limited ability to pick and choose what you're running.

      I don't want Evolution. I don't want Tomboy, and I certainly don't want Beagle.

      If I really wanted MS interop, I'd just buy a stinkin' Windows machine.

    19. Re:FUD by GreatBunzinni · · Score: 1


      You may have plenty of reasons to criticize Miguel de Icaza but that sure isn't one of them. He invested his time in a project, he worked on it, the end result of his work is better than most people's work. That has absolutely no reason to criticize someone. On top of that, the end result is FLOSS, which means that anyone can just pick up where he supposedly stopped and keep driving it further. There's no wrong with that.
      Besides that, I don't believe any software project is ever finished. There is always the need to fix this, implement that, tweak something... There is always stuff to do. It's yet another reason why your criticism targeted at Miguel is silly.
      And to top things off, as you are criticizing the man who contributed to and had/has a decisive participation in quite a few software projects that are very influential in the free software world, care to compare your resume to Mr Icaza's? And I don't mean where you went to school or what was your grade point average. I mean, care to compare your contributions to the FLOSS ecosystem with mr Icaza's? After all, if you feel entitled to put up such self-righteous indignation regarding a man's contributions then you must have plenty of moral authority on the subject.
      And last but not least, do you happen to know that Linus Thorvald wrote the basis of Git and once the project was up and running he abandoned it in the hands of some other people for them to pick it up where he left? Knowing that, do you also feel that you should attack mr Thorvald's contributions for being also "pathologically incapable of working on something until it's mature"?

      --
      Slashdot, fix your code or at least hire someone who is competent at it to do it for you.
    20. Re:FUD by Logi · · Score: 1

      (although this spat on /. might bring it to MS attention.)

      If that is of even the least concern, then Mono should not be in Debian.

      This is all just a bit funny to us old farts who remember why gnome was originally created.

      --
      Logi - I can do anything, but not everything.
  59. Windows.Forms works just fine! by PRMan · · Score: 1

    What are you talking about? Windows.Forms works just fine and (to me) is the way to go if you want to develop cross-platform applications in C#.

    The only part to watch is interacting with the file system. Everything else just works.

    --
    Peter predicted that you would "deliberately forget" creation 2000 years ago...
    1. Re:Windows.Forms works just fine! by Malc · · Score: 1

      I guess I'm behind the times! I don't use Mono, just regular .Net on Win32. That really shows how much crap the OP was spouting.

  60. Mod parent up .. by argent · · Score: 1

    Informative...

  61. troll much? by atropa · · Score: 1

    riiiight.. because we all know how lax Debian/GNU is about their patent/license concerns compared to Red Hat.

    --
    moo
  62. Re:Good by recoiledsnake · · Score: 1

    IronPython runs on the .NET framework. Dunno about Mono though.

    --
    This space for rent.
  63. Re:Slow news day by _Sprocket_ · · Score: 1

    When Microsoft offer an unlimited patent covenant for all distributors of Linux software, people will stop complaining about it overnight.

    Then maybe those other distros need to go talk to Microsoft and secure themselves a covenant like Novell did.

    And then Microsoft becomes the gatekeeper the critics are afraid they'll be.

  64. Let's compare bloat! by Anonymous Coward · · Score: 2, Interesting

    Since .NET is an entire platform "just like Java", let's compare their bloat.
    The latest version of the Java runtime is 15.50 MB big. And it will run apps written for *any* version of Java.
    The latest version of the .NET framework is 231 MB big. And it will only run apps written for that version, requiring the "side by side" installation of other runtimes for other versions.

    1. Re:Let's compare bloat! by binarylarry · · Score: 1

      It should be pointed out that Mono is yet ANOTHER variant of .NET, that isn't full compatible with any of the versions released from Microsoft.

      So on Windows, you get a copy of each .NET runtime version plus a copy of each Mono runtime versions.

      It's the attack of the Java clones!

      --
      Mod me down, my New Earth Global Warmingist friends!
    2. Re:Let's compare bloat! by Draek · · Score: 1

      Now let's compare functionality! because the Mono runtime is around 15 MBs big so I *guess* Microsoft's framework includes more than just the basic .NET runtime.

      Also, IIRC 3.5 will run any code compiled for 2.0 or above, its just 1.0 stuff you need the older runtime for.

      --
      No problem is insoluble in all conceivable circumstances.
    3. Re:Let's compare bloat! by man_of_mr_e · · Score: 2, Interesting

      Where do you get 231MB? That's the size of the full "redistributable" installer, including compilers, debugging tools, debug versions, etc. The actual size of the 2.0 runtime is 22.4MB

      http://www.microsoft.com/downloads/details.aspx?FamilyID=0856EACB-4362-4B0D-8EDD-AAB15C5E04F5&displaylang=en

      That's not 3.5, but 3.5 is a superset of 2.0, which is basically adding on stuff that the basic JRE doesn't have anyways like Workflow and WPF.

      Also, why is it that Java also creates side by side installations? I have something like 15 Java versions installed because each update installs a new version. Each Java folder is about 90MB, which means it's taking up about 1.35GB.

      And you are wrong. The latest version, 3.5 SP1 will run 100% of apps from 3.5, 3.0, 2.0, and about 99% of 1.1 and 1.0 apps. Side by side installations are not required except for a very tiny fraction of 1.1 and 1.0 apps that had a breaking change occur.

  65. Re:Yessss by blackest_k · · Score: 1

    Trolls don't discriminate, just because somebody makes crazy threats doesn't mean they actually believe in what they are saying or are supporters of one faction or another. some people just want to stir things up just for the sake of it. Mono's interesting it could be useful but its risky to build it into a core package without being sure that it can't be used as a lever against Linux. Anyone who is aware of the history of Unix and how it was taken away from the very people who developed Unix should be able to understand that viewpoint. Mono certainly isn't essential just yet and perhaps some distributions holding back is a good thing. If microsoft is wanting net to be a success across platforms you'd think they would be willing to clarify their stance, if there is no intention of using it against Linux or other operating systems.

  66. Re:Yessss by Anonymous Coward · · Score: 1, Informative

    No. Distributors cannot "ignore the bloody things" because unlike hobby developers, they're commercial entities and Microsoft will sue them to death as soon as they start making money by distributing something that include Microsoft-patented technologies.

    That's exactly what they've just done with TomTom and FAT (and that patent even was, unlike the ones on .NET, pretty weak).

    Moreover, there is difference between a patent-ridden application and a patent-ridden execution environment. In the first case, should problems surface, we could just drop the offending application. In the second case, we would have to drop ALL applications running on that environment. (And by the way, those applications would keep running on Windows, so guess where would all "orphaned" users be forced to go?)

    So, given the fact that there we already have perfectly equivalent technologies without the same dangers, the less .NET-based applications are there on Linux, the better.

  67. Yes, it's troll summary. by recoiledsnake · · Score: 2, Informative
    From http://www.figuiere.net/hub/blog/?2009/04/06/657-gnote-010 See first comment by a Fedora maintainer:

    Monday 6 April 2009 15:39, by Rahul Sundaram :: # For Fedora, we had to remove tomboy from the live cd due to lack of space. Unfortunately, Gnote probably won't be a good replacement since it would pull in the gtkmm, boost and other dependencies. Have you considered Vala or PyGTK instead?

    So the summary includes the dependencies for Tomboy but not for Gnote. If you add up gtkmm and boost and other dependencies, it might get close to 50MB. The summary is a troll for comparing apples to oranges.

    --
    This space for rent.
    1. Re:Yes, it's troll summary. by Anonymous Coward · · Score: 1, Informative

      I am Rahul Sundaram, maintainer of Gnote in Fedora that you are quoting from. We did manage to include Gnote as the default replacing Tomboy in Fedora 12. For one, GNOME system monitor already is using gtkmm and boost has been split in Fedora 12 to be more granular.

       

    2. Re:Yes, it's troll summary. by Xabraxas · · Score: 1

      Mono is only 25MB. Boost is 24MB and gtkmm is 16MB. The dependencies for Gnote take up more space than the dependency of Mono for Tomboy.

      --
      Time makes more converts than reason
  68. Re:Slow news day by Anonymous Coward · · Score: 0

    >So how many more years of them not suing anyone over Mono is it going to take

    infinitely many, logically. If Microsoft would write that they won't, that would be a way for the people to "shut up".

    >always around the corner waiting to sue people for Mono

    >as open and willing to work with the FOSS community on Mono as one can really expect from a company like this.

    Willing to work with the FOSS community _for now_.

    I'm not sure what's so hard to understand, Microsoft is a company. They don't work with others for the fuzzy feelings and kinship.

    And from a business standpoint it makes sense to be cautionous of other companies turning around to stab you, especially if it is Microsoft (which does that all the time).

  69. Re:Good by Abreu · · Score: 1

    Python is 18 years old... quite a long time for a "fad"

    --
    No sig for the moment.
  70. Dancing with the Devil in the pale moonlight by Anonymous Coward · · Score: 0

    ... why does this feel like these Distros are "dancing with the devil" in that I can't imagine building open source on top of someone else's patents is a good idea.

  71. Not so fast... by Anonymous Coward · · Score: 0

    KDE4 already has C# bindings.

    It's a matter of time before some "revisionist" starts using them.

    1. Re:Not so fast... by ultrabot · · Score: 1

      KDE4 already has C# bindings.

      It's a matter of time before some "revisionist" starts using them.

      There are C# bindings for Qt, but I doubt they are of interest to many - mostly because "native" Qt coding doesn't suck.

      --
      Save your wrists today - switch to Dvorak
  72. Re:Victory for Free Software Advocates by AlexMax2742 · · Score: 1

    It's a victory for great free software applications that just so happen to use Mono. Mono often gets treated as a second class citizen because of its Microsoft roots, with zealots not wanting Microsoft's "unholy embrace" on Linux, whatever that's supposed to mean. Thankfully, there are sane people to defend it and because of this developers don't have to worry about their software not being included in a default install because they just so happened to pick Mono.

    Also, how was my original post Flamebait?

    --
    I'm the guy with the unpopular opinion
  73. Re:Red hat/Fedora improve, Debian/deb-based regres by Anonymous Coward · · Score: 3, Informative

    Just so everyone else isn't snowed by this post, Fedora has not dropped mono and currently has no plans to, they have only said "we'll continue to look at it with our legal counsel to see what if any steps are needed on our part". The recent push to include mono based Banshee by default instead of Rhythmbox in Fedora and Ubuntu was caused by the one of the main Rhythmbox developers saying that rhythmbox has "several limitations" and that he was going to "still fix (some) bugs and review patches, but it's too much of a dead end for me to do more than that", leading many to believe it is in maintenance only mode. Not, as the parent says "Mono zealots".

  74. Re:Yessss by Mr+Z · · Score: 1

    Can't they just do what every other free software project does, and just ignore the bloody things?

    There are two kinds of infringement under US patent law: Ordinary infringement and willful infringement. Guess which one carries triple damages? If you know something is covered by patent protection and you still infringe upon the patent willfully, you could be liable for triple damages. There are ways to keep the enhanced damages associated with willful infringement at bay (such as "advice of counsel," where you have expert legal advice to the effect that the patent is believed invalid), but that's something of a crap shoot.

    So, how you act once a patent has been brought to your attention matters. In this case, it sounds like there are at least a couple .NET related patents that could apply to Mono. Infringing on those patents in the absence of legal counsel advising us that those patents are invalid would amount to willful infringement.

    Don't take my necessarily-inaccurate-because-it's-a-sound-bite version's word for it. Here's an interesting article from the American Bar Association on the current state of this ever-evolving topic.

  75. Please stop spreading misinformation by Anonymous Coward · · Score: 0

    I have already written 3 days ago about why almost everything that is told in this news is wrong. In the end, this is just a bait for Boycott Novell zealots who have nothing better to do of their lives.

    http://np237.livejournal.com/23901.html

  76. Re:Victory for Free Software Advocates by Anonymous Coward · · Score: 0

    How is it a victory when there is another application that does *all* the same things except that it doesn't need the tons of dependencies?

    By all means, let the tomboy developers enjoy working on their thing, and let everyone who likes it use it, but I could think about a couple of things I'd like those 40MBs used for other than Mono

  77. Re:Yessss by ais523 · · Score: 1

    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.

    Actually, I suspect they signed it because Microsoft offered them lots of money to do so. Imagine Microsoft offered to pay you $1000 and also give you a patent licence to Mono. Would you accept their offer? Would that then mean that you believed Mono required a patent licence to use?

    --
    (1)DOCOMEFROM!2~.2'~#1WHILE:1<-"'?.1$.2'~'"':1/.1$.2'~#0"$#65535'"$"'"'&.1$.2'~'#0$#65535'"$#0'~#32767$#1"
  78. Mono but not Firefox? by Parker+Lewis · · Score: 1

    So, Debian can include Mono, but not Firefox due the Logo license? I think Mono has a lot more copyrighted stuff than the Firefox logo.

    1. Re:Mono but not Firefox? by Anonymous Coward · · Score: 1, Informative

      You think wrong. Mono is 100% Free Software.

    2. Re:Mono but not Firefox? by Tetsujin · · Score: 1

      You think wrong. Mono is 100% Free Software.

      And it's all copyrighted...

      Patents are the "worry".

      --
      Bow-ties are cool.
  79. It isn't unethical by Anonymous Coward · · Score: 0

    Or is Microsoft's use of the BSD TCP stack unethical???

    You can't put your code out under a share license and complain when someone takes what you've shared and ports it unless the port cannot be shared likewise.

  80. waste of a modpoint on an IBM fanboy by Anonymous Coward · · Score: 0

    yeah i said it

  81. Re:Slow news day by gbjbaanb · · Score: 1

    however, the covenant as set forth above will continue as to specific copies of Covered Products distributed by Novell for Revenue before such update

    so.. the stuff Novell gives away for free is not necessarily covered by the 'lets be good' bit of the covenant? that's more scary to the F/OSS community than any other part of it.

    So MS could turn around tomorrow and say to any company that used Mono "we're suing" and they'd be within their rights. I doubt MS would sue anyone over Mono - they're too busy enticing Linux developers with "just have one go, just to see what all the fuss is about. Its sooo easy, you'll feel great developing using it" that they prefer the benefits of getting Linux devs to consider some cross-platform development using Mono.

    However, I feel that if they see themselves losing the netbook or mobile OS space, they will do everything they can to reclaim it, using any and every weapon they have. Nobody thought MS would sue over VFAT - that everyone uses for their flash drives, but they did.

  82. Re:Mono is a gateway to cross-platform virii by Curien · · Score: 1

    Hopefully, you'll effect a change in his future posts.

    --
    It's always a long day... 86400 doesn't fit into a short.
  83. Re:Good by drewness · · Score: 1

    IronPython runs on the .NET framework. Dunno about Mono though.

    The Mono package for MacOS X comes with IronPython. I haven't really tested it, but it does at least start. I don't see why it wouldn't work essentially the same as on Windows, except maybe with GUI stuff, if there's some Windows.Forms classes that Mono hasn't implemented yet.

  84. Re:Victory for Free Software Advocates by AlexMax2742 · · Score: 1

    By all means, let the tomboy developers enjoy working on their thing, and let everyone who likes it use it, but I could think about a couple of things I'd like those 40MBs used for other than Mono

    Open up a shell and type in: $ man mt

    --
    I'm the guy with the unpopular opinion
  85. Re:Slow news day by Anonymous Coward · · Score: 0

    Mono is part of OIN. They won't open that can of worms. Actually that is much more proof for not sueing than most other applications/libraries have. As not having sued is not a proof for not suing in the future, not knowing of a patent infringement doesn't mean there is none.

  86. The Real Question is by HermMunster · · Score: 2, Insightful

    What the hell is tomboy doing as a dependency in the first place? It's a totally unnecessary package which I have absolutely zero use for.

    --
    You can lead a man with reason but you can't make him think.
    1. Re:The Real Question is by PhrkOnLsh · · Score: 1
      That's what metapackages do: They pull in an entire working DE, whether you want all the applications or not.

      apt-get install kde installs a BUNCH of crap as well.

      Which is why no one should ever install those metapackages in the first place. Tomboy isn't getting included in the default install, only in the GNOME metapackage.

      --
      GNU/Linux: Freedom.
  87. Only good thing about Mono by Dareth · · Score: 1

    The only good thing about Mono is that you may have gotten it from kissing a girl!

    --

    I only look human.
    My mother is a halfling and my dad is an ogre, so that makes me an Ogreling
  88. What should be in every Linux default install by ThatsNotPudding · · Score: 1

    http://tim.thechases.com/mononono/

    RMS is kind of an intolerant jerk, but I think he does have a point. Linux could end up dying at the hands of well-meaning, easily manipulated pollyannas and Benedictian insiders who took the money and ran.

  89. Re:Victory for Free Software Advocates by HermMunster · · Score: 1

    There are reasons the linux industry doesn't want Microsoft's code involved, primarily the "embrace, extend, extinguish" tactic. Also the 235 alleged patent violations and the threat to industry that if they use linux they'll have to pay Microsoft, sometime. Also the fact that the industry doesn't want to be tainted. Many don't even want to look at Microsoft's code and certainly don't want it in the fold.

    It's more a matter of self preservation rather than puritanical perspective that keeps Microsoft at a 1000 foot pole's length.

    --
    You can lead a man with reason but you can't make him think.
  90. Re:Red hat/Fedora improve, Debian/deb-based regres by SCHecklerX · · Score: 1

    I think I'd have to agree with the OP. Ape-ing microsoft is not where I'd personally like to see linux and its various desktop environments go. I'd prefer we do it *better*. Evolution, as far as I see it, is the former. Same goes for mono.

    Example, with nautilus. WHY does nautilus do the copy/paste/rename cycle for making a copy of a file via GUI? The way ROX Filer (as an alternative example) does it is so much more elegant. On copy action, you can rename the file with a dialog that pops up and then drag to the location of your choosing. One step vs. 3 kludgy ones. Yeah, you could keep the microsoft copy behavior, and even add that ROX type stuff, but nautilus chose to do only the former. The restrictive 'scripts' directory is also annoying. This is supposed to be a flexible environment, dammit. Why do I have to have all of my apps I want to run from a menu in a specific place, ordered by name??? Windowmaker does this so much more elegantly. One reason I like linux is the flexibility and the 'fun' of being able to do things more suited to the way I like to work. That is being eroded by things like your beloved evolution and mono based apps.

    If only all environments would take the best ideas from the others and choose to either get rid of or push aside the other stuff.

  91. KDE and Gnome by Tetsujin · · Score: 2, Insightful

    *On another note: What's the point of Gnome again, now that Qt/KDE is open sourced?*

    To not be a cluttered piece of crap, which is KDE's job. See on UNIX, every program should do one thing and do it well.

    I've always thought KDE's applications were much better than OpenOffice - and Gnome doesn't seem to have any productivity applications at all...

    (I've run mostly KDE for a long time, though I have been running Gnome of late, on my new laptop - and I'm quite enjoying it...)

    I really strongly feel that Unix lacks the coherent infrastructure needed for this "each tool does one thing well" philosophy... If each tool does just one thing, then your ability to accomplish things strongly depends on how effectively and easily you can link multiple tools together... I feel like the old Unix tools philosophy has gone AWOL of late, and it's pretty much absent from the GUI space, where an individual application is usually written to handle all possible actions for an individual problem domain, and there's very little consideration made to linking these applications together...

    --
    Bow-ties are cool.
  92. Re:Slow news day by shutdown+-p+now · · Score: 1

    When Microsoft offer an unlimited patent covenant for all distributors of Linux software, people will stop complaining about it overnight.

    Given that "all distributors of Linux software" includes e.g. IBM, I think that such a deal could only go on a reciprocal basis (i.e. IBM offers an unlimited patent covenant to Microsoft) - otherwise Microsoft would just screw itself royally by unilaterally disarming its defensive patent portfolio.

    And, compared to the above scenario, I think that snowball's chance in hell is pretty damn good.

  93. Re:Victory for Free Software Advocates by Aphoxema · · Score: 1

    I'm afraid mono-anything really is a second class citizen; Microsoft is widely untrusted, they actively have attacked and still attack anything not-Microsoft, they arm themselves and let people know it and the only incentive they have to not destroy opposition outright are the legal barriers they don't forget about.

    Now imagine a citizen, a walking, breathing citizen walking around acting like this.

    I do not doubt the defenders are perfectly sane, it is their legal and historical experience I do not trust.

    --
    "Most people, I think, don't even know what a rootkit is, so why should they care about it?"
  94. Re:Red hat/Fedora improve, Debian/deb-based regres by PhrkOnLsh · · Score: 1

    I think I'd have to agree with the OP. Ape-ing microsoft is not where I'd personally like to see linux and its various desktop environments go. I'd prefer we do it *better*. Evolution, as far as I see it, is the former. Same goes for mono. If only all environments would take the best ideas from the others and choose to either get rid of or push aside the other stuff.

    First off, I don't use evolution, I only cited it as an example.

    Second, this is not about "ape-ing" anyone. It's about getting the job done and creating great applications that rival Microsoft and other desktops. What tool someone uses should be a nonissue, in the long run. There is little issue with the Mono runtime, it's been around since (believe it or not) before the Novell Microsoft agreements, it has had no legal trouble in the four years of its development, and there is little reason that it should. This simply comes down to the issue of what a developer wants to develop from, and nothing more.

    What if Microsoft had created C++? Would you be shunning GNotes?

    If it wasn't the Gnotes developer that had started this little war, I may be more open to consideration of the issue, but there is a HUGE COI in that, imo. Comes across to me that he is just trying to get back at the Tomboy team because they made it into the dependancies and not him. And instead of one-upping the application with new features, etc, he decides to simply attack the framework which the application is based on.

    And, for the record, I don't use any mono applications; I just have the ability to look at things objectively and not judge things on the company that may or may not be related to a piece of software's development language. Modding the OP +4 insightful just goes to show how narrow minded /. commenters really are.

    --
    GNU/Linux: Freedom.
  95. What is the point? by FranTaylor · · Score: 1

    Does C# offer compelling features over Java? Why do we waste our time building the same bridge twice? Java and C# go way out of their way to have nothing to do with each other, so it's not like there is some mutual benefit or that they learn from each other.

    Java is really just a spec and people are free to implement it how they want. There is tremendous opportunity for vendors to be creative under the covers and provide all manner of functionality within the Java framework. This can be done with or without Sun's blessing, and there is a healthy competitive market for Java infrastructure.

    On the other hand, C# is a Microsoft Platform and you pretty much have to buy into their thing if you want to get serious.

    1. Re:What is the point? by PhrkOnLsh · · Score: 1

      Why do we waste our time building the same bridge twice?

      Hold on, I'll go get you your x86 assembler.

      --
      GNU/Linux: Freedom.
    2. Re:What is the point? by Abcd1234 · · Score: 1

      Does C# offer compelling features over Java?

      Actually, yeah. Just as a language, C# is nicer than Java (and I say this as someone who's written a fair share of Java) in a few ways, although admittedly a lot of it is syntactic sugar. That said, proper closures, alone, are with the switch to C#. Anonymous inner classes, you can go to hell.

      But where Mono really wins is on the API front. Because Mono leverages a ton of existing OSS projects, one can use familiar, native libraries for doing GUI development (GTK), database access, sound and video, and so forth. Contrast this with Java, where JNI is the exception rather than the rule, and in general you're stuck with Java's "weird", Java-specific toolkits for various things.

      So, you have two high-level languages. They're essentially the same (with C# offering some notable improvements), but on the platform side, Mono integrates extremely well with the system, while Java tries to stand separate and alone... personally, I'll take the former over the latter any day.

      On the other hand, C# is a Microsoft Platform and you pretty much have to buy into their thing if you want to get serious.

      Really? Funny... I've used Mono off and on for little toy projects, and I've never once had to using anything from the System.Windows or Microsoft namespaces. In fact, Mono provides a complete OSS-backed application stack, including GUI toolkit, database layer, XML processing, and a whole host of other APIs.

      So... what exactly are you talking about?

  96. Re:Red hat/Fedora improve, Debian/deb-based regres by Lorien_the_first_one · · Score: 1

    I'd like to know how that works out as I'm planning on doing the same (Ubuntu 9.04 64-bit---> Fedora 11 32-bit). Reason? My DVD writer will no longer read/write DVD/CDs. This was a brand new machine when I bought it. And I've seen a lot of forum posts complaining about this.

    I'm also not too keen on promoting Microsoft technologies. Even if they *have* been submitted to the ECMA. After watching what they did with OOXML at the ECMA and then ISO, I'd rather avoid the drama.

    --
    The diversity and expression of human opinion is essential to human survival.
  97. Re:Mono is a gateway to cross-platform virii by Anonymous Coward · · Score: 0

    Runs in a safe VM
    No buffer-overflows
    No crashes due to uninitialized memory
    No dangling pointers

    Unless you use unsafe.

  98. Knobs by Brandybuck · · Score: 1

    This is where source based packaging makes sense. With a source based system (FreeBSD, Gentoo, etc) you have "knobs" to give you a little control over the dependencies. Thus you can have a GNOME without Mono. But with binary packages you are stuck with what the Committee decides you need.

    --
    Don't blame me, I didn't vote for either of them!
  99. My own very stupid reasons for not liking Mono by Tetsujin · · Score: 1

    Free software relies on all kinds of sources. The GNU system itself was/is a re-implementation of UNIX. Many of the languages used started off as proprietary. There's nothing new in this. Where is the campaign to purge Fortran or Pascal from the free software opus? Why no campaign against Samba and the use of the SMB protocol? Why is nobody outraged at DotGNU? Where are the calls to cease supporting .avi container and other MS developments?

    The difference there, to my mind, is the extent to which we come to rely upon these various technologies. If the Samba project were defeated through legal measures by Microsoft (and please don't interpret this as a suggestion that this will happen - it's just a scenario.) then what would we lose? One LAN file sharing protocol out of many, the ability to share files over a LAN with Windows machines without installing any additional software on the Windows machine...

    Mono (or DotGNU, if anybody actually used it) present a somewhat different problem: here you've got something which (IMO anyway) Linux sorely lacks: a coherent VM implementation that can be used in the implementation of different scripting languages, a consistent data representation that can be used to help bind different languages together, and additionally C#, which seems like a good language for application development. This places it in a much more critical position if one comes to rely upon it.

    It's hard to debate with people when their fundamental position is composed essentially of hatred, fear and dislike of persons or groups. Where is the factual basis? Where is the ability to consider anything useful when hate or fear is the driving force? This is religion by another name, it cannot be reasoned with, it is impervious to contradictory verifiable fact, it allows no deviation.

    There is no contradictory verifiable fact. In the end, Microsoft will either use legal means to defeat Mono, or not. Nothing they say or do now actually prevents this from occurring. Likewise there's not much in the way of "factual basis" apart from what Microsoft has done in the past. You are right that this is largely about fear: though personally I am not entirely convinced that this fear is entirely unfounded. Sometimes there's not a lot of solid information to rely upon: in that case there's no choice but to guess, gamble at what will and won't happen in the future.

    Personally, I feel like Mono is not necessarily what I signed on for when I chose to use Linux in the first place. It's a petty reason, really, but even such simple things as putting ".exe" on the end of a filename, or using the same file type signature as DOS executables - these aren't things I really want to see on my system. It gives the programs a bit of an alien character. I don't think it's especially sensible in general for compiled programs to run in a VM, for that matter. Matters of taste like this may seem silly but they are relevant, to my mind: if things don't fit my own idea of what I'd like Linux to be, as a system, then I generally won't be too inclined to stand behind them.

    Really, any time you try to introduce some critical piece of infrastructure to the system, people will be hesitant to invest themselves in it - they need to be convinced that it's the right thing. Any facet of the system that people don't like will count against it, and stand in the way of people adopting it. It's not enough for a bit of technology to be good - people have to embrace it or its merits won't make a difference.

    It's a tough problem for a platform where there's no central authority - how does one make the platform as a whole advance at a fundamental level, when there's no one to lay down the law about how the core components will work? Groups like Gnome or KDE or major distributions like Debian or Ubuntu are about the closest thing we've got to an "authority" to make these decisions stick - honestly it makes me a bit uneasy that Gnome has gone with

    --
    Bow-ties are cool.
    1. Re:My own very stupid reasons for not liking Mono by julian67 · · Score: 1

      A reasoned opinion, well expressed. Like a breath of fresh air.

      My understanding (I may be wrong and am happy to be corrected) is that the worst that Microsoft could do would be to extend .NET in ways that make projects built on mono incapable of being compatible with .NET. They can do this without any "attack" on mono as it currently exists. As far as desktop applications go it's pretty much a non-issue or a minor issue because cross compatibility with Windows .NET isn't the goal of the typical mono application. It would be a bigger issue if mono was, like Sun's Java, the basis of important enterprise applications. That doesn't seem to be the case. Again I'm happy to be corrected and to be shown those widely used cross platform enterprise tools.

      And what would happen if *somehow* mono itself was directly attacked, perhaps becoming the subject of litigation in the way BSD was, becoming so surrounded with uncertainty that it gains de facto untouchable status?

      Gnome and various developers, in house and independent, would have wasted some time and resources. Tomboy is not the only note tool, F-Spot is not the only photo manager and Beagle is not the only meta-search tool. Whatever the merits or otherwise of these applications they are clearly attractive to users, distributions want to ship them and developers evidently enjoy improving them. But none of them is necessarily irreplaceable. Existing installations would continue to work, the end users would not immediately be disadvantaged. The issue then becomes "what are the replacements?". At that point I'm left wondering why the vociferous opponents of mono have singularly failed to create applications with the same appeal. I'm not sure porting Tomboy to C++ is exactly inspirational. The one truly effective and practical act that would negate mono would be the development of applications with the same appeal to users and distributions and the Gnome project. Tracker is a reasonable substitute for Beagle. Despite being a fan and a user of Gthumb and Geeqie I wouldn't have the bare-faced cheek to claim they are drop in replacements for F-Spot or even claim to have similar goals or features in many important ways. One has to doubt the potential longevity of Gnote, given that it exists principally as a protest and offers nothing new in the way of ideas or presentation.

      btw I don't run any mono apps :-)

       

    2. Re:My own very stupid reasons for not liking Mono by Tetsujin · · Score: 1

      My understanding (I may be wrong and am happy to be corrected) is that the worst that Microsoft could do would be to extend .NET in ways that make projects built on mono incapable of being compatible with .NET.

      Really, I don't think anybody would know what Microsoft could do against Mono until/unless they tried... It would be all about how the lawsuit plays out - what's happened so far may not have a great deal of influence upon that.

      I don't at all know how likely it is that Microsoft would even try to damage Mono. It seems to me that it all depends on whether they felt they had something to gain from it.

      It would be a bigger issue if mono was, like Sun's Java, the basis of important enterprise applications. That doesn't seem to be the case.

      It's still fairly new. We may have simply not reached that level of reliance upon it yet. But a tool like Mono - if people aren't relying on it, then it means we're not yet fully taking advantage of it.

      Consider the .NET versions of Python and such, for instance: they offer some nice advantages, particularly in terms of integrating Python code and data with code written in other languages. I believe, for instance, that it's quite straightforward to write a Powershell commandlet in IronPython. This is a practical benefit of the .NET platform that Linux doesn't share because of limits in how people are apparently willing to utilize Mono at this point. You won't generally find IronPython on Linux systems, let alone in place of CPython... (Does it even work on Mono? I don't know...)

      Gnome and various developers, in house and independent, would have wasted some time and resources. Tomboy is not the only note tool, F-Spot is not the only photo manager and Beagle is not the only meta-search tool.

      It's important to look at what that means for those applications now, however: uncertainty about Mono translates to these applications. I know I don't want to invest myself in any photo-management application that I would be unable to rely upon in the future. If I started using F-Spot to manage my photos and then had to stop using it, I don't know where that would leave me in terms of the organization of my photos.

      In practical terms, though, I feel like the greater danger is always simply that the package maintainers will simply stop working on the project. That's a risk that exists for any such app, independent of any perceived Microsoft threat.

      The one truly effective and practical act that would negate mono would be the development of applications with the same appeal to users and distributions and the Gnome project. Tracker is a reasonable substitute for Beagle. Despite being a fan and a user of Gthumb and Geeqie I wouldn't have the bare-faced cheek to claim they are drop in replacements for F-Spot or even claim to have similar goals or features in many important ways.

      Well, it's a lot of work to write an application like that - and for the most part I think it's a waste of time. The motivated developer talent in Linux is spread thinly enough, I think, without having to rewrite perfectly good applications. (Though to a certain extent this is unavoidable - different teams will often take on the same problem and come up with "competing" solutions, each with different advantages - it takes time for any kind of clear winners to emerge...)

      --
      Bow-ties are cool.
    3. Re:My own very stupid reasons for not liking Mono by julian67 · · Score: 1

      I think that's a good summary of the anxieties of end users.

      "the greater danger is always simply that the package maintainers will simply stop working on the project."

      That's something real and within most people's experience. Yet it doesn't stop us happily using all kinds of stuff which may be deprecated/abandoned in a few years. And a common event, especially with proprietary applications, is the breaking of backward compatibility. Still it doesn't deter many people. So my guess is that as mono and mono-based applications *are* free software and *are* distributable and *do* offer distributions and end users and developers applications that appeal and a development environment that appeals then it will take more than the fear and uncertainty to hold it back. Something like a protracted legal dispute (one with actual expensive lawyers involved as opposed to one involving bloggers screaming or bizarre campaigns of slander against individual developers) or a decision by either the FSF or the OSI that mono doesn't meet their definitions of Free or Open Source software. Unless that happens then the people who oppose mono are really wasting their breath.

    4. Re:My own very stupid reasons for not liking Mono by Tetsujin · · Score: 1

      I think that's a good summary of the anxieties of end users.

      "the greater danger is always simply that the package maintainers will simply stop working on the project."

      That's something real and within most people's experience. Yet it doesn't stop us happily using all kinds of stuff which may be deprecated/abandoned in a few years.

      Well, in my case it does. :) At least it did when I was thinking of getting set up with some iPhoto-like software... F-Spot's the only one I liked enough to keep it installed - but I didn't go to the extent of cataloguing all my old photos or importing new ones. I should really rethink that, one of these days... F-Spot could very well be the one that's worth the time and effort.

      Something like a protracted legal dispute ... or a decision by either the FSF or the OSI that mono doesn't meet their definitions of Free or Open Source software. Unless that happens then the people who oppose mono are really wasting their breath.

      I wouldn't exactly say they're wasting their breath. They have their own idea of how Linux as a platform should evolve, and to them Mono isn't a part of it. They are advocating (if not in a particularly nice way) their own idea of how things should move forward, and they are having an impact.

      The unfortunate bit is that this whole conflict over Mono doesn't get us anywhere. It's progress, in one direction or another, which improves and advances the platform. If Mono were more universally adopted by Linux users, I think that would be a good thing for the platform. For people who want to write commercial applications it represents, among other things, a fairly stable ABI... For the rest of us, it could be a good system infrastructure component - if our culture can accept it.

      But there's my dilemma - I feel the Linux platform would benefit from having some more powerful and version-stable components standard - even just from a "hacker" perspective that's valuable. Improving inter-language binding is very valuable, as is providing a generic mechanism applications can use to generate optimized code at runtime. Likewise the potential implications for IPC, application scripting, and so on are all grand. So I believe having a "core component" that does roughly what Mono does would be a great asset. Any candidate that can provide that functionality would be a good thing, and the main criterion that discerns how useful it is would be the adoption rate. So from that perspective, I should stand behind Mono as the prime candidate of a means of providing that functionality - except that I don't like the character of that particular solution, and that matters to me. So it's either embrace something I don't really like to try to promote the benefits it will bring, or don't embrace it, and hope something else that's "more Linuxy" will fill roughly the same role on Linux as .NET does on Windows. But it would take some serious time for all that to happen... like years...

      --
      Bow-ties are cool.
  100. Patent problems outlined by Jerry · · Score: 1

    http://en.wikipedia.org/wiki/Mono_(software)

    Mono consists of three groups of components:

          1. Core components
          2. Mono/Linux/GNOME development stack
          3. Microsoft compatibility stack.

    The Microsoft compatibility stack provides a pathway for porting Windows .NET applications to Linux. This group of components include ADO.NET, ASP.NET, and Windows.Forms, among others. As these components are not covered by ECMA standards, some of them remain subject to patent fears and concerns.

    Mono's implementation of those components of the .NET stack not submitted to the ECMA for standardization has been the source of patent violation concerns for much of the life of the project. In particular, discussion has taken place about whether Microsoft could destroy the Mono project through patent suits.

    The base technologies submitted to the ECMA, and therefore also the Unix/GNOME-specific parts, may be non-problematic. The concerns primarily relate to technologies developed by Microsoft on top of the .NET Framework, such as ASP.NET, ADO.NET and Windows Forms (see Non standardized namespaces), i.e. parts composing Mono's Windows compatibility stack. These technologies are today not fully implemented in Mono and not required for developing Mono-applications. Richard Stallman has claimed it may be "dangerous" to use Mono because of the possible threat of Microsoft patents.[9]

    On November 2, 2006, Microsoft and Novell announced a joint agreement whereby Microsoft agreed to not sue Novell's customers for patent infringement.[10] According to Mono project leader Miguel de Icaza,[11] this agreement extends to Mono but only for Novell developers and customers. It was criticized by some members of the free software community because it violates the principles of giving equal rights to all users of a particular program...

    --

    Running with Linux for over 20 years!

  101. Why not just use a text editor? by PenisLands · · Score: 1

    Myself, I don't see the need for tomboy or anything like that. If I want to keep notes, I make a text file in my home directory and edit it with gedit or some other text editor. It's much faster, just as convienient, and doesn't require any special software.

  102. Some words from the packager. by delire · · Score: 1
    This post from the packager himself sheds light on the matter.

    Of course, the real discussion around including Mono by default is not about Tomboy. If they donâ(TM)t want of it, the debian-installer team just has to include GNote in the gnome-desktop task to get it by default instead of Tomboy; note that this is possible since I added an or dependency, precisely as you suggested. No, the applications that are going to make a difference are things like GNOME Do and F-Spot. If we want to include these cool applications that have no real alternative (even proprietary), this will include the Mono stack as well. And there are no stripped down C++ versions of those.

    and..

    The reason why Tomboy was not included in the default Lenny installation is not because of stupid software patents. If we gave a shit of inapplicable software patents, we wouldnâ(TM)t be shipping MP3 decoding software by default. If we gave a shit, we wouldnâ(TM)t ship Mono in main, regardless of what is in the default installation. We donâ(TM)t give a shit of where is Mono coming from, as long as it is free software. As Jo explained, we donâ(TM)t even give a shit of what Mono is, it just happens to be a dependency for Tomboy. No, the reason why Tomboy was not here by default is simply because its dependency stack was too big for some installation media. Now, the Debian Mono team managed to reduce a bit the installation size, and the availability of GNote as an alternative is giving a last-resort choice that will be much smaller.

    1. Re:Some words from the packager. by iggymanz · · Score: 1

      I care where mono came from, Microsoft is big enough and rich enough to come up with a way to make trouble. And I don't want nor need .NET or C# crapware on my machine. Plenty of languages can be used instead. So fuck mono.

  103. Mono is a disease by Technomancer · · Score: 1

    http://en.wikipedia.org/wiki/Infectious_mononucleosis

  104. Re:Mono is a gateway to cross-platform virii by K.+S.+Kyosuke · · Score: 1

    Well, at least some of the things you have mentioned do not seem to bother Smalltalk people at all, and Objective-C was designed to appeal particularly to them. (Typesafe generic coding in a language with mutable state, what a joke! Smalltalkers are clever and don't even try.)

    --
    Ezekiel 23:20
  105. Re:Slow news day by Anonymous Coward · · Score: 0

    What would stop them if they should decide to sue?

    aptitude remove?

  106. What's the best alternative Distro? by HiThere · · Score: 1

    What's the best alternative distro to Debian? Fedora isn't really aimed at desktop users, Ubuntu is also going to be including mono by default. Etc.

    I think that I'd be able to hash things around to avoid mono anyway, but I'd rather not have to hassle with that, so what's the best alternative? Space isn't my problem, but I'd really rather avoid mono, and I need an end-user distribution.

    --

    I think we've pushed this "anyone can grow up to be president" thing too far.
    1. Re:What's the best alternative Distro? by iggymanz · · Score: 1

      the mainstream distros that use GNOME will have mono. you could always use one of many other desktop managers. I don't want anything to do with C# or Microsoft's diseased crap either

  107. Re:Mono is a gateway to cross-platform virii by setagllib · · Score: 1

    The JVM has far more languages than the CLR, several of them far better than C#. Scala for example makes C# look like QBASIC. Java as a language may be stalled, but the JVM as an open platform is currently unbeatable, especially by Mono.

    --
    Sam ty sig.
  108. I have no problems with Mono in its place by Xtifr · · Score: 1

    It's not that I hate Mono--I just don't want it inflicted as a dependency of one of the standard (the better of the two big, IMO) Linux desktops. People who want/use Mono, like people who want/use Java should be free to install it and run it for whatever they want, and share free (and Free) apps amongst themselves, but I've already got about a dozen programming languages and runtimes installed, and I DO NOT WANT OR NEED this huge, bloated monstrosity (hugeness, bloatedness and monstrousness all confirmed when I manually purged the beast after the last time some lame dependency dragged it onto my system).

    Heck, I came within inches, last year, of using Mono for a port from C#/.NET to Linux, and I would have been perfectly happy if that's the direction we'd chosen (although I'm pleased to say that our C++ port is working beautifully now), but I still don't want it embedded into my desktop!

  109. This is getting old... by Anonymous Coward · · Score: 0

    I realise the media are ... slow, don't do their research, and like to cause a scene, but seriously - how long does it take people to understand that mono is not implementing anything patented, or even worthy of being patented.

    The classpaths it does implement are overly generic (if patents get to the point of patenting a string, process, or window... so help me...) - and the non-generic ones it uses (eg: ASP.NET) use Microsoft's own shared source code, under their own shared source license (without breaking it) - and the rest, are all mono/posix/unix specific classpaths anyway.

    Get a brain, and a life... seriously.

    Shame on you all.

  110. Obligatory... by Tetsujin · · Score: 1

    I once thought I had Mono for an entire year. Turns out I was just really bored.

    --
    Bow-ties are cool.
  111. It seems to me, I suppose.... by jotaeleemeese · · Score: 1

    Why should Linux projects live with the uncertainty, specially when Ballmer has spelled, in no uncertain terms, what he thinks about Linux and the precious MS "intellectual property".

    I just don't get it why so many Linux and FOSS heads are so eager to ingratiate themselves with Microsoft. It reminds me of people that are into abusive relationships....

    --
    IANAL but write like a drunk one.
  112. There is a big difference. by jotaeleemeese · · Score: 1

    MS's CEO made specific patent trolling threats against Linux in no uncertain fashion, combine this with their "agreements" with Novell and other Linux packagers and you know what they are aiming at.

    --
    IANAL but write like a drunk one.
    1. Re:There is a big difference. by telemachuszero · · Score: 1

      MS's CEO made specific patent trolling threats against Linux in no uncertain fashion, combine this with their "agreements" with Novell and other Linux packagers and you know what they are aiming at.

      They no doubt have patents that cover aspects of the Linux kernel, Xorg, MESA, KDE, GNOME, and just about every other layer of the system. As others have stated, if the Mono project is notified of patent infringement, they will resolve it by either reimplementing in a way that avoids the patent, or remove the functionality if there is no way around it. The same as the other projects will handle it if it is brought to their attention and they want to continue distribution in the US.

  113. That is the way MS wants you to think. by jotaeleemeese · · Score: 1

    Microsoft has not put forward a single bit of evidence about somebody in the Linux world infringing their precious patents (where software patents apply, there is still hope that in vast swathes of this planet such lunacy is not allowed to happen).

    That is why so many of us dislike Novel, Xandros & co with a passion: they gave credence to Microsoft's position without the monopoly abusers having to do as much as to say which patents they have been talking about.

    Novell has given mixed signals about the deal, and have declared in many occasions that they are not infringing any patents, in which case one just don't understand why they got into bed with Microsoft in the first. Protection (have you seen any gangsters' movie?) comes to mind....

    So to reiterate, no, nobody in Linux land has accepted that there is any infringing code in Linux. Educate yourself and stop to spread this unsubstantiated rumour.

    --
    IANAL but write like a drunk one.
  114. The problem is not technical. by jotaeleemeese · · Score: 1

    I want a legally binding document in which Microsoft assures the Linux community that they will not attempt to screw up Linux development for, most likely bogus, patent infringement claims.

    If they really want to show some good will I want to hear their lawyers, not their developers and Engineers (all of them very cool people I am sure).

    --
    IANAL but write like a drunk one.
  115. You say that like if ISO standards... by jotaeleemeese · · Score: 1

    ... were worth the paper they are written in.

    After the procedure witnessed during the approval of another ISO "standard" pushed by Microsoft, it is quite rich to name ISO as something to look for as worthy.

    --
    IANAL but write like a drunk one.
  116. Such old canards .... by jotaeleemeese · · Score: 1

    Is anybody controlling Fortran or Pascal threatening Linux with patent litigation? No.

    CIF (the protocol behind Samba) predates anything Microsoft came with network wise. This is well documented, so I don;t see what your point actually is. If anything the Samba team have to bend over backwards in order to accommodate the capricious ways MS treis to use the CIF protocol.

    You can say whatever you want about the reasons why people don't like Mono. I met Miguel a couple of times, he is a very nice, clever and enthusiastic chap, but he is completely misguided about trusting Microsoft. The bodies of competitors and, more worryingly, former business partners should tell you all what you need to know about collaborating with that company.

    But lets say I am deluded. But surely I did not imagine the public threats against Linux made by Ballmer and his accolades regarding patents.

    Any bogus patents claims will have to start in places where Microsoft has a foot in the door. They will not start with sendmail, bind ro any other targets in which clearly they haven't had any input, but the threat would clearly come from somewhere where they are calling the shots.

    Any .Net technology has the potential to be the trojan horse MS uses to attack Linux.

    SCO showed what a real PITA it can be to defend against bogus claims, just imagine what MS could do if they decided to throw a hissy fit.

    Everybody not realising this is naive to an extreme that is inexcusable.

    --
    IANAL but write like a drunk one.
  117. Re:Slow news day by bonefry · · Score: 1

    I'm not aware of any proof on the contrary.
    You can pick any related story about VFAT you want, it still doesn't say anything about Mono.

    What would stop them? How about a dozen other companies with similar patent portfolios?

  118. ...but please don't throw me in the briar. by Anonymous Coward · · Score: 0

    Microsoft have no intention of suing Debian. Their agent, Miguel, is doing fine work, making Gnome dependant on Microsoft technologies and that is the whole point of this exercise.

    Mono is already required by F-Spot photo manager which many Gnome users are dependant on. Pretty soon Debian will be riddled with other mono dependencies and there will be no easy backing out of it. Once Debian is undermined, Ubuntu will be down and out for the count.

    Never underestimate the reach and power of a company which has tens of billions of dollars sitting in the bank.

  119. Re:Open formats concerns are hardly FUD by Klistvud · · Score: 0

    Being concerned about non-free frameworks such as .NET is almost as important as supporting Open Document Format as opposed to .doc and other proprietary formats. Many software users are very aware of the freedom-limiting and encumbering nature of proprietary software solutions, such as avi, flash, jpeg, .NET and so on. I never quite understood why so many people never give a damn about being on the legal side of things; they actually prefer, say, a pirated copy of MS Office as opposed to the free equivalent, OpenOffice. Maybe because in the Windows world, there is hardly any distinction, since most of the time "free" means "warez" anyway? This semi-legal attitude is supported by the industry: I am virtually prevented from converting all my CD's to .ogg for listening to on-the move, because hardly any portable music player supports .ogg! Of course, on certain players you can install a software player that supports .ogg, but the fact is nevertheless severely limiting to people who prefer legality as opposed to the patent-encumbered mp3's. Moreover, the .NET framework is superfluous not only because of its "legal" status, but also from the bloatware point of view: having to run yet another slow, bloated, RAM- and CPU-hungry runtime at every boot -- and for what: just for being able to run a tiny yellow sticky-notes applet? No, thanx. The Java runtime is enough. And free. And better.

    --
    Intellectual Property: an immaterial non-entity, most fiercely contended by those with no proper intellect to speak of.
  120. Re:Yessss by Anonymous Coward · · Score: 0

    If there's such a thing as legitimate patents, .NET ones are certainly a good example of MS making an investment in innovation and appliing for patents to protect it. And you compare that with "one click to buy" junk. Very appealing...

  121. Already Covered by True+ChAoS · · Score: 1

    Theres an exceptional rebuttal against the rampant naysayers posted here by one of the members responsible for the Debian/Mono integration: http://www2.apebox.org/wordpress/rants/124/

    --
    WARNING: May contain traces of nut
  122. The plan to divide and conquer by Ilgaz · · Score: 1

    IMHO MS has a better plan than patent trolling for future with the Mono project and its puppets paid to work (or simply stupid enough) working on it.

    In Helloween docs, specialist reporting for Microsoft puts Linux'es strengths like very advanced command line and how impossible to implement them on Windows.

    Of course, the one weakness has been reported. A community which is easy to divide even with political arguments.

    Right after that report, first KDE got hit by not being GPL (an argument still being used) or the Library it relies on is not being totally free and Gnome started. Icaza... That is one division still lives and effects Linux today.

    After years when Novell had serious issues that even non tech people argued whether they will go chapter 11 or straight out of business, they deal with Microsoft accepting their terms and hire Icaza.

    Microsoft does a last attempt to gain back its users giving them something that is claimed to work anywhere but being Windows only. The functionality developers love and rely on starts with 'win' like windows forms. Right while people jokes with the framework and even MS only shops reject to be bound to it, some half ass working thing ships named 'Mono' supposed to be cool open source name of Microsoft .NET. Today, MS .NET is 3.5 SP1 (stable) and 4.x betas started to be talked about, people actually use 3.5 features and Mono is stuck somewhere as 2.x. Guy behind it is Icaza again.

    Silverlight ships, becomes industry joke because of the lack of multi platform support while Adobe seriously readies 'one flash for all' concept which will work even on handsets, same guy pops up and pulls the exact Mono scheme. ''1 major version behind but open source (in OUR terms)''. Just like .NET MS also have a good argument when sane people asks ''Shouldn't you be OS neutral when you try to race with Java?'.

    As Debian took this decision to allow that trojan to their distro, all my respect to their freedom standards, ethics, perfectionism has all gone. They should join Icaza when he goes to Redmond instead of celebrating their own OpenSUSE major release.

    One more thing I can't stand not saying in this long message... Gotta respect to Apple. Even in their darkest days, they have put a boundary, a limit.

    For Linux, we still have Volkerding and Slackware to rely on.

  123. C# as in C right? by Ilgaz · · Score: 1

    You write in something including 'C' in its name right? You write programs so you should know why the C language was invented and designed from start.

    So far, it has delivered its promise as the real multiplatform compiled language.

    Can you point your apps OS X, Linux, FreeBSD downloadable binaries so I can run them? If I sound like asking too much, Opera which is written in 'bulky' language runs the very same core both on my 8 Gig Quad G5 and Sony Ericsson P1i smart phone having 128MB RAM and also right on this Mac Mini G4.

    You can say ''I prefer C# because all my audience is running Windows (Mo)'' but please, please don't even use C/C++ in same context as that Microsoft abuse of C.

  124. BOGUS! by Whitemice · · Score: 1

    THERE ARE *NO*, *ZERO*, *ZILCH* "specifications patented by Microsoft and licensed under undisclosed terms" used in Mono. *NOTHING* is "licensed" from Microsoft for use in Mono by anyone at all.

    When will the flaming @*^$*&^@ ignorance stop?

    Do people realize that a software patent that applied to Mono would almost certainly apply to Java? And very possibly GLIBC? Maybe even X? Or GCC? And that Microsoft holds patents that relate to HTML, AJAX, and CSS? Get your heads out of your collective asses and learn what your talking about - or shut the hell up.

    --
    Using "Common Sense" is being either to arrogant or to ignorant to ask people who know more about something than you.
  125. Re:Open formats concerns are hardly FUD by Whitemice · · Score: 1

    Being concerned about non-free frameworks such as .NET is almost as important as supporting Open Document Format as opposed to .doc and other proprietary formats.

    Why? Contrary to the article: *NO* "specifications patented by Microsoft and licensed under undisclosed terms" for use in Mono. This is confusion by the ignorant of the M$/Novell deal with Mono, the two have nothing to do with each other. The Samba team works very closely with M$, has accepted code from M$, and M$ testes Samba on M$ servers... should Samba be excluded from Debian?

    Moreover, the .NET framework is superfluous not only because of its "legal" status, but also from the bloatware point of view: having to run yet another slow, bloated, RAM- and CPU-hungry runtime at every boot -- and for what: just for being able to run a tiny yellow sticky-notes applet? No, thanx. The Java runtime is enough. And free. And better.

    Better how? Have you done benchmarks? Run some, you'll be suprised.

    --
    Using "Common Sense" is being either to arrogant or to ignorant to ask people who know more about something than you.
  126. Why oh Why by medoc · · Score: 1

    Even if c# is marginally better than java or python or (insert favorite opponent here), this seems a really weak reason to insert a huge piece of Microsoft property into the heart of Free Software. I can't understand why Mono has happened and why this contamination is going on.

  127. Re:Incredible horrifying bloat, or useful features by Tetsujin · · Score: 1

    Or what's the "old and understood" method for an application to receive notification when the disk is full? Or when a USB device is inserted?

    I agree with the above sentence (and I completely agree with the GP, he nailed it on the head). The problem I see with modern distros (modern GNU/Linux) is that many of those features that somebody "needs" are being hacked into the system without really thinking about the big picture. Basically, we're just hacking extra stuff into GNU/Linux that somebody wants to have now, because she saw it in a different OS and it seemed nice.

    Could you elaborate upon that? Like what's an example of such a system? Why is it not necessary? Or why does it not fit in with the rest of the system?

    I have to admit I'm still not too familiar with a lot of this stuff - for instance I don't know much about hald except that it delivers hotplug notifications and such, and most of what I know about dbus I learned yeaterday after a cursory google search. But from what I know so far it generally seems like good stuff.

    --
    Bow-ties are cool.
  128. There's more to it: by itomato · · Score: 1

    This Mono encumberance spreads via dependencies. Installing GNOME or certain GTK apps without any Mono dependencies is extremely difficult. Even more so when these packages and dependencies are tested and become part of stable, yielding silly situations, like when 'bootsplash' is replaced with 'splashy', which requires the 'gnome-desktop-environment' meta-package, 'gnome-desktop', 'cheese', etc.

    From what I've seen and read, the dependencies in Debian are being swept in as a means to resolve inter-package dependencies within Debian. It's GNOME and subcomponents, and some tertiary apps that require Mono, but oversight in keeping barriers between 'default' and 'encumbered' is falling short, despite claims to the contrary:

    http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=473118

    "This is why gnome-desktop-environment doesn't depend on it despite being
    part of the official GNOME desktop.

    The gnome metapackage is here to bring a full-fledged desktop with all
    the bling. If you don't want everything, you should install
    gnome-desktop-environment and pick other stuff depending on your choice."

    As it happens in some other distributions - SUSE, for instance, the dependency web is such that basic GNOME components have a cross-dependency with Tomboy, and as GNOME is headed by Mono-centric developers, it's to be expected that the interoperability of GNOME components will continue to depend on Mono. Evolution, Tomboy, Beagle, will each require similar effort as has been put into Gnote, and similar vigilance in assuring compatibility.

  129. Take with a grain of salt: by itomato · · Score: 1

    http://www.novell.com/linux/microsoft/faq_opensource.html

    Q8. What does this mean for Mono and its inclusion in non-SUSE distributions? Does Mono infringe Microsoft patents?

    "We maintain that Mono does not infringe any Microsoft patents. This agreement does not impact the rights and abilities of other distributions to bundle and ship Mono.

    Novell is the leading contributor to Mono and we remain committed to the Mono project. Mono is a community project with many constituents and collaborators from companies, universities, governments and individuals.

    The Mono project has a set of rules it uses to handle patents that might read on its implementation. The general policy is to work around, remove, or find prior technology on any patents that might read on any implementations in Mono. We continue to support this policy."

    Also,
    http://www.mono-project.com/FAQ:_Licensing#Patents

    " Could patents be used to completely disable Mono?

    First some background information.

    The .NET Framework is divided in two parts: the ECMA/ISO covered technologies and the other technologies developed on top of it like ADO.NET, ASP.NET and Windows.Forms.

    Mono implements the ECMA/ISO covered parts, as well as being a project that aims to implement the higher level blocks like ASP.NET, ADO.NET and Windows.Forms. ...The core of the .NET Framework, and what has been patented by Microsoft falls under the ECMA/ISO submission. Jim Miller at Microsoft has made a statement on the patents covering ISO/ECMA, (he is one of the inventors listed in the patent): here (http://web.archive.org/web/20030424174805/http://mailserver.di.unipi.it/pipermail/dotnet-sscli/msg00218.html)

    Basically a grant is given to anyone who want to implement those components for free and for any purpose."

  130. Re:Slow news day by JSBiff · · Score: 1

    "Mono is part of OIN."

    Mono is a Novell/Ximian product, not a Microsoft product. Unless I'm mistaken, Mono being part of OIN doesn't put ANY legal restrictions on what Microsoft can do. So, I don't see how Mono being part of OIN really has anything to do with whether or not Mono is 'safe' for use by developers and end-users?

    I've been trying to read more about this the last couple days, and from what I can find, the 'core' Mono/.Net technologies are apparently considered pretty 'safe' because Microsoft published it as part of an ECMA standard. I guess that provides some protection against lawsuits about that (I'm not really sure, though - I'm not a lawyer, and all that).

    Still, there is some question surrounding the ASP.net, ADO.net, and Windows.Forms parts of Mono.

  131. Stallman and Mono by Conrad+Mazian · · Score: 1

    One of the claims used to push Mono was that Stallman was OK with it. He has just recently issued a statement that he is against mono being included in Linux distros.