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."
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.
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.
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.)
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.
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.
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. 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 [debian.org] 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.
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.
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.
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?:)
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.
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?
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 [figuiere.net] released 2009-04-29 adds applet support. Why use Tomboy at all now?
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.
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!
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.
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.
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.
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 [wikipedia.org], 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.)
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?
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.
"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.
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/ [wordpress.com]
So his complaints would all be still valid, unless he's biased against mono.
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.
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.
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.
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.
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.
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:
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.
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.
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.
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 extensio
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.
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 [java.net].
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.
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.
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".
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.
by Anonymous Coward
on Monday June 15, @09:00AM (#28334619)
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.
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.
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.
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?
Frist (Score:4, Interesting)
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.
Re:Frist (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.
Parent
FUD (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.)
Parent
Re:FUD (Score:4, 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.
Parent
Call Upon the ECMA Code of Conduct (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.
.NET, MIcrosoft does hold at least one patent [uspto.gov] 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 [msversus.org]. No one seems to be clear on how you get this into writing [itwire.com] but it's allegedly the way things are.
.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 [debian.org] 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.
Even though Microsoft submitted the CLI [ecma-international.org] and C# [ecma-international.org] main components of
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
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.
Re: (Score:3, Informative)
Re:Call Upon the ECMA Code of Conduct (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.
Parent
Re:Call Upon the ECMA Code of Conduct (Score:5, 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?
Parent
Re:Call Upon the ECMA Code of Conduct (Score:5, Interesting)
Parent
Re:Call Upon the ECMA Code of Conduct (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 [freshmeat.net]
Parent
Re:Call Upon the ECMA Code of Conduct (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 [figuiere.net] released 2009-04-29 adds applet support. Why use Tomboy at all now?
Parent
that's irrelevant (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.
Parent
Re: (Score:3, Funny)
Default installation? (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.
Re:Default installation? (Score:4, Funny)
OS News reports that Debian developer Josselin Mouette got Tomboy accepted as a dependency for gnome
Parent
Incredible horrifying bloat (Score:5, 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?
Re: (Score:3, Insightful)
Re:Incredible horrifying bloat (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.
Parent
Re: (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.
Re:Incredible horrifying bloat (Score:4, Insightful)
Except these other programs are not included as a gnome dependency...
Parent
Re:Incredible horrifying bloat (Score:4, 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.
Parent
Re:Incredible horrifying bloat (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 [wikipedia.org], 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.)
Parent
Re:Incredible horrifying bloat (Score:4, 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?
Parent
Re:Incredible horrifying bloat (Score:4, 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.
Parent
Re:Incredible horrifying bloat (Score:5, Insightful)
.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
Parent
Re:Incredible horrifying bloat (Score:5, Informative)
Parent
Re: (Score:3, Insightful)
Re:Incredible horrifying bloat (Score:5, Informative)
Parent
Looks more like Sid (Score:4, Informative)
The commit was done on Debian unstable, which is Sid, not Squeeze.
What the F... (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.
Re:What the F... (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.
Parent
Re:What the F... (Score:5, Insightful)
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.
Parent
Re:What the F... (Score:4, Insightful)
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.
Parent
Re:What the F... (Score:4, 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.
Parent
An interesting read on the subject (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/ [apebox.org]
Re: (Score:3, Insightful)
Re:An interesting read on the subject (Score:5, Insightful)
As long as Microsoft retains any control over
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.
Parent
Re:An interesting read on the subject (Score:4, Insightful)
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
Recently, thought, Mono has gained a few improvements over
Personally, not holding my breath, and I don't want Mono on my machines.
Parent
Re: (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 extensio
Another good reason to use KDE (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
what a troll (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.
Re:what a troll (Score:5, 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 [java.net].
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.
Parent
Try Gnote instead of Tomboy (Score:5, 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.
Wrong. (Score:3, 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".
awkward fact, may ruin exciting story (Score:5, Informative)
http://svn.debian.org/viewsvn/pkg-gnome/desktop/unstable/meta-gnome2/debian/control?revision=20303&view=markup [debian.org]
"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.
Re:Yessss (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.
Parent
Re:Yessss (Score:4, Insightful)
Parent
Re:Yessss (Score:4, Informative)
Parent
Re:Yessss (Score:4, 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.
Parent
Re:Slow news day (Score:4, 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?
Parent