[Mono-devel-list] Re: [Mono-list] Surveys: Mono 1.0 and MonoConference.

Todd Berman tberman at gentoo.org
Sun Oct 12 21:54:35 EDT 2003

> Yes, but I still don't see why you couldn't say, release mono core 1.0
> because its ready, and release GTK# a month later when it stabilizes.
> (I'm not implying that GTK# is more or less ready then mono core, just
> an example). What I'm trying to say I guess is that some parts might
> ready before other parts.

GTK# is already released independently of mono.

> I understand this too. I didn't say that some of these packages
> depend on each other. What my suggestion is, is that some platforms
> don't need all of the tools, so make it easy not to install them, and
> the same time, we might be able to release some of the packages before
> others. For example, I'm sure MCS is getting close to stable and that
> ASP.NET, being much newer, is not quite as close. By having a separate
> ASP.NET release, we can release MCS sooner and release ASP.NET a
> later.

Here is where I think you misunderstand.

System.Web is a base class library that contains (basically) ASP.NET.

Are you suggesting that mono gets released without System.Web?

That will then leave a lot of developers insanely confused, as that
class contains not only ASP.NET stuff, but also stuff like: the SMTP
mail client classes. And while that isn't such a huge issue, what
happens when someone who doesn't really understand whats going on goes
and downloads a C# application that uses that namespace, and it wont

And saying that 'MCS' can be released is insanely misleading.

MCS itself is a 1.2MB application, which is by no means an indication of
the size of mono. MCS itself *relies* on the corlib, which is 3.7MB
alone. And even a copy of mono with just the corlib and mcs is going to
be found pretty lacking by any standards.

So, can you please clarify exactly what you mean by releasing MCS and
then releasing ASP.NET separately?

> I'd rather have the stable parts of mono asap and wait for the less
> stable parts rather then have to wait for everything to stabilize.

Mono is already stable enough for development, just download the latest
release, and even better, show us the bugs you find, and we can make it
even more stable even faster.


More information about the Mono-devel-list mailing list