Linked by Thom Holwerda on Fri 14th Mar 2008 20:41 UTC, submitted by John Mills
Thread beginning with comment 305060
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]: Mono is good/evil?
by fithisux on Sat 15th Mar 2008 18:00
in reply to "RE[2]: Mono is good/evil?"
RE[4]: Mono is good/evil?
by Bending Unit on Mon 17th Mar 2008 21:52
in reply to "RE[3]: Mono is good/evil?"






Member since:
2008-03-14
I'm glad that you like it! Here are a couple of answers/additions to some of your points:
Good #2: We don't actually use WinForms on Windows, though MD can run on Windows and Mac. We're pro-GTK!
Good #4: Agreed, C# and the class library are awesome. C# 3 is even cooler, and Mono now supports it (though MD doesn't yet).
Good #5: MD can both generate and synchronise makefiles too, so even if you don't want to use them, you can distribute them. MD has a command-line build tool too.
Bad #1: The debugger's a major priority for the next release. We've been waiting for a stable release of the Mono debugger library.
Bad #2: Instability is likely to be a problem with an old version of GTK# (Ubuntu?). MD is very stable on recent GTK# versions.
Bad #3: As the developer of MD's ASP.NET support, I'd be interested in hearing what you'd like from the ASP.NET support in future versions. Code completion is in development, but the visual designer is on hold pending a stable release of WebKit-GTK.
Bad #4: Actually, the 2.0 support is near-complete and very stable. The 2.0 runtime in particular has been usable for a very long time -- MD itself has been built and running on the 2.0 profile for almost two years. The only significant part of 2.0 that's still not complete is WinForms 2.0.