A couple of applications from your future desktop [LWN.net]

A couple of applications from your future desktop

Posted Oct 21, 2004 4:58 UTC (Thu) by simon_kitching (guest, #4874)
Parent article: A couple of applications from your future desktop

Interesting that it is built in MONO, and that the developers plan to integrate it with nautilus and dashboard.

Is this intended to be a project "outside" the gnome core project, has the decision to include MONO in Gnome been taken, or are they just hopeful?

to post comments

Stop the insanity and drop Mono now

Posted Oct 21, 2004 5:13 UTC (Thu) by LinuxLobbyist (guest, #6541) [Link] (4 responses)

Yes, that is what I'm wondering as well.

Let the assimilation begin.

I've read the arguments, and I don't buy them. Miguel and the other Mono proponents are completely ignoring history. If M$ can figure a way to crush FOSS, it will. This just gives them a toehold to do just that.

While M$ might not succeed in crushing FOSS with the Mono toehold, the potential for the need to rewrite large portions of GNOME if Mono takes hold among developers of core GNOME apps could be devastating. Mark my words, it WILL happen.

Stop the insanity and drop Mono now

Posted Oct 21, 2004 8:10 UTC (Thu) by walles (guest, #954) [Link]

The CLR (and thus Mono) is designed to be able to run programs compiled from many different languages, C included.

Thus, in the long run there's nothing preventing Gnome from both running inside of Mono and being written in C to a large extent.

See http://www.go-mono.com/languages.html#c for example.

Stop the insanity and drop Mono now

Posted Oct 21, 2004 23:13 UTC (Thu) by massimiliano (subscriber, #3048) [Link]

Miguel and the other Mono proponents are completely ignoring history.

No, we're not.

The only weapon Microsoft could have against Mono is software patents.

If you look carefully, those nice applications do not use "the Microsoft stack" of .NET libraries. They are based on the ECMA standards, and on wrappers on the Posix and Gnome libraries. The ECMA standards do not have patent issues from Microsoft, and the other libraries... well, every Gnome application would be using those libraries anyway! Look into that, Mono provides (and uses) wrappers for GTK, Mozilla, Posix... if there were patent issues, they would not be in the wrappers, but in the libraries themselves, so I state it again, every application using them would be at risk. Using Mono makes no difference.

Add to this Novell's patent policy (which is intended to minimize the risk that somebody actually starts a patent war against open source projects, including Mono)...

So no, the issue is not been overlooked. And chances are that any other technology that does similar things would be covered by the same patents, including Java (seen the Kodak disaster?), and why not, the new perl interpreter, parrot. At the very least the Mono core is covered by the ECMA standard!

Stop the insanity and drop Mono now

Posted Oct 22, 2004 1:43 UTC (Fri) by bronson (subscriber, #4806) [Link] (1 responses)

OK, I'm willing to mark your words. If Microsoft hasn't managed to crush Mono in 5 years, then will you admit you were wrong? And, if they do, I'll admit I was wrong. Personally, I don't think they'll even try; talk about a low percentage effort. Note that quibbling over the .NET emulation libraries is very possible, but that doesn't matter because Gnome software doesn't use them.

Without a time limit, your prediction has about as much meaning as "the end of the world is coming!" i.e., not much.

Stop the insanity and drop Mono now

Posted Oct 22, 2004 4:00 UTC (Fri) by LinuxLobbyist (guest, #6541) [Link]

Five years is reasonable. And, yes, of course I'll admit I'm wrong if it doesn't happen. But with a caveat: only if the policies of the USPTO do not change for the better (i.e.: disallow or severely limit the award of software patents). If the policies change for the better, my assertion becomes moot.

I think many people forget how easy it is for an extremely wealthy company with a near inexhaustible supply of money can game the patent system as well as standards bodies. And it's only getting worse. Witness what happened with the IETF MARID Working Group for but one example. I was (am, actually, but the traffic is near nil, now) subscribed to that list as well as spf-discuss before that and warned of getting too close to Microsoft very early on. And look what happened.

I don't know much about ECMA, but having parts of .NET in the hands of a standards body doesn't give me much comfort, given what I've seen from some standards bodies.

And Microsoft doesn't have to be *right* if they make any kind of claim against Mono in order to hold it in limbo in court for years and drain the financial resources of those who back it and/or distribute it. I personally know people who Microsoft did just that to.

Novell's new patent policy is extremely commendable. It'll likely have an effect against SCO-like (but with patents added) suits of the future. But against the Microsofts of the world, we'll have to see.

Mono

Posted Oct 21, 2004 6:10 UTC (Thu) by ncm (guest, #165) [Link] (6 responses)

Maybe Mono is handy for prototyping, but these things should be re-implemented in a real language before trying to deploy them. There's nothing like depending on an unstable, immature execution environment to brand a program as buggy, slow, piggy, etc. (Witness Freenet!) Rewriting in modern C++ on libgnomemm ought to be easy, instructive, and maybe even fun.

Mono

Posted Oct 21, 2004 8:03 UTC (Thu) by walles (guest, #954) [Link] (4 responses)

On the other hand, the only way to turn Mono into a stable, mature runtime environment is for people to develop apps on top of it, find problems with it and have them fixed.

Even gcc wasn't very good to begin with.

Mono

Posted Oct 21, 2004 8:21 UTC (Thu) by ca9mbu (guest, #11098) [Link] (1 responses)

> On the other hand, the only way to turn Mono into a stable, mature runtime
> environment is for people to develop apps on top of it, find problems with
> it and have them fixed.

Which is why this quote from the original article:

> Among other things, it seems there are memory leak problems in Mono which
> have to be worked around

strikes me as very odd. Why work around the problem at all? If the guys developing beagle have found a memory leak, why can't they report it and have it fixed upstream so it can be fixed and they don't need to work around it at all?

Mono

Posted Oct 21, 2004 22:51 UTC (Thu) by massimiliano (subscriber, #3048) [Link]

In fact the memory leaks are being fixed...

Mono

Posted Oct 21, 2004 17:16 UTC (Thu) by ncm (guest, #165) [Link] (1 responses)

Why bother making the Mono runtime stable and mature at all? Maturity isn't really needed for prototyping, and just interferes with the process of transitioning those prototypes to a real language.

Mono

Posted Oct 22, 2004 7:02 UTC (Fri) by walles (guest, #954) [Link]

That's a circular argument.

You're saying that since Mono isn't mature, it isn't good for anything but prototyping. And since it's only good for prototyping, why should it be made mature?

The answer is of course that *if* Mono should become stable and mature it would be good for other things than prototyping. And since it would then be good for other things than prototyping it would need to be stable and mature :-).

As is explained on "http://www.go-mono.com/languages.html", your definition of a "real" language would have to be quite uncommon to be able to find a language that couldn't potentially be run by Mono.

mono is quite mature

Posted Oct 22, 2004 12:02 UTC (Fri) by louie (guest, #3285) [Link]

I have my own issues with mono, but if you're criticizing the maturity or stability of mono, you obviously haven't actually used it. I have run tomboy 24x7 for a couple weeks now, and muine 24x7 for several months now, on a music box which is never rebooted and on which muine is never turned off. Neither have had memory or stability problems. There may be plenty of criticisms you can make of mono, but that's just not one of them.