Linked by Thom Holwerda on Thu 12th Feb 2009 08:05 UTC, submitted by poundsmack
Thread beginning with comment 348418
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Monkey see, monkey do
by abraxas on Thu 12th Feb 2009 14:25
in reply to "RE[2]: Monkey see, monkey do"
Yes, but my point is that it IS already integrated. As a Ubuntu-Gnome (default install) user I have to actively remove it.
Ubuntu isn't GNOME. Blame Ubuntu for the integration, not GNOME.
From my POV the mono developers are spending all of their time chasing a moving target, instead of creating something new. Make mono better than .net (do keep compatibility with clr/il) - don't just copy it.
It seems like you haven't been paying attention. Mono has been doing exactly that for years.
100% agree - so start building upon it! (boo stands out - but is independent of mono, afaik.).
Boo is a language just like C#. They both run use the CLR. Using boo doesn't change anything. C# and the CLR are standards. It's the Microsoft compatibility libraries that people are worried about but they are not necessary for Mono to exist. In fact the Linux applications you know that use Mono DO NOT use any of those libraries.
RE[3]: Monkey see, monkey do
by jstedfast on Thu 12th Feb 2009 14:25
in reply to "RE[2]: Monkey see, monkey do"
Mono already is innovating and better than Microsoft's .NET in a number of ways (in fact, they're copying our features now!)
Mono has cutting edge features like SIMD optimizations and an interactive C# shell (Microsoft has announced that they will be adding a C# interactive shell for .NET 5.0 which won't be out until 2012)
Mono also had Mono.Addins long before Microsoft released their Microsoft Extension Framework.






Member since:
2005-07-06
Yes, but my point is that it IS already integrated. As a Ubuntu-Gnome (default install) user I have to actively remove it.
Isn't it the task of microsoft to make sure that mono is compatible with microsoft?
From my POV the mono developers are spending all of their time chasing a moving target, instead of creating something new. Make mono better than .net (do keep compatibility with clr/il) - don't just copy it.
100% agree - so start building upon it! (boo stands out - but is independent of mono, afaik.).
btw, mono could not use the CLR implementation? - only the specification?
All of these are self contained and follow no direction as pointed out by others (except some open standards (w3c, c-specs etc). I understand what nyou're trying to say - but I dont think these compare. Perhaps if apache was an implementation of IIS and they kept copying features from IIS, then I would see the similarity.
Edited 2009-02-12 12:20 UTC