Linked by Thom Holwerda on Tue 7th Jul 2009 08:51 UTC, submitted by PLan
Mono Project We've already seen some heavy discussion on Mono and C# here on OSNews the past few weeks, as it became clear the patent situation regarding the ECMA parts of Mono was anything but faith inspiring. This issue seems to be resolved now: Microsoft has made a legally binding promise not to sue anyone who uses or distributes implementations of said ECMA standards. Following this news, Mono will be split in two; the ECMA standard parts, and the rest.
Thread beginning with comment 372083
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: On Mono
by google_ninja on Tue 7th Jul 2009 13:20 UTC in reply to "On Mono"
Member since:

Not to mention the technical deficiencies like encouraging closely coupling your program to native libraries, the inelegance of putting x86 DOS code into the header of every .NET program, and the mess of a standard library.

P/Invoke is the absolute last resort in .net, just like JNI is for java, to say its "encouraged" is completely false. And .net compiles to IL, which get JITd to native code on the first run, just like java and bytecode. I think someone has been feeding you lies.

In my opinion, if we must use a statically-typed interpreted language, we should go with Java. Some folks have been maintaining Gtk/GNOME bindings for Java (, why not give them a try?

Because Java sucks? There are fewer and fewer people even in the java world that like java, which is why there is such an interest nowadays in stuff like scala, groovy, and javafx.

Java vs C#, C# is the clear and obvious winner. When it comes to static languages, scala is IMO the most elegant, modern, and downright cool language around nowadays. And while I haven't gotten into it too much yet, javafx looks like a fantastic language for UI, much better then general purpose languages.

Edited 2009-07-07 13:24 UTC

Reply Parent Score: 2