Linked by Thom Holwerda on Sun 11th Jan 2009 10:54 UTC, submitted by Hiev
Mono Project Arstechnica reports that Mono, an open source implementation of .NET runtime, is bringing Microsoft's development technologies to some unexpected places, including the iPhone, Android, and the Wii.
Permalink for comment 343147
To read all comments associated with this story, please click here.
RE: wow, i mean just wow....
by adkilla on Mon 12th Jan 2009 15:25 UTC in reply to "wow, i mean just wow...."
Member since:

Getting upset about .exe and .dlls's, being windows-specific things brought into Linux(and other platforms)-seems on the surface to be really, really silly.

You might want to read my post here before jumping to that conclusion:

Adkilla if I understand you correctly you are lamenting at once a) the fact that Mono has implemented a bunch of MS only kludges which have no bearing in a cross platform world and b) the fact that mono has not completely implemented each and every specific .Net tech. To be honest with ou I have no idea how Mono could not be guilty of a) if they do a good job at b). Seems to me like it is a no-win situation for Mono from your perspective. (If I misunderstood you please correct me)

Mono was never a complete implementation of .Net and will never be. They are constantly playing catch up with MS while trying to fit .Net cross platform.

Instead of cherry-picking .Net functionality that works well cross-platform and innovating the rest on their own, they have decided to be a incomplete copy-cat. I strongly believe that Miguel and his talented team are capable of innovating away from MS to provide a better alternative that works as well if not better. I also believe that Mono would be much more attractive if it were to promote itself as cross-platform CLR with a well designed framework, than a mere .Net copycat with a sub-par cross-platform design.

I will give an example where there were initiatives to make Mono more than .Net. The #WT initiative was a good example. But the insistence of Mono stay the course with System.Windows.Forms killed it. Failing to make S.W.F useable with native L&F on platforms other than Windows, they decided to take the Cocoa#/GTK# course instead. If they were to stick with #WT, it would have been a real cross-platform contender GUI wise. But no, they decided to take the half-baked approach instead. Till this day they do not have unified cross-platform GUI frameworks that Java enjoys.

From my involvement with many experienced .Net developers, I've learnt that they are aware of Mono but consider it an inferior copy that attempts to bring .Net to Linux. Some (like me) have expressed that they would switch to Mono in a heartbeat if Mono would steer their own course. Heck, we would even switch fully to Mono and dump .Net (even on Windows), if Mono would try be an elegant framework and runtime (that is compatible with MS CLR) that works cross-platform as its goal. Some of us took the attempt to share this with the Mono team over IRC to only be shot down. We could understand that Novell has now put themselves in a licensing situation with MS over .Net patents that would make it hard for them to back down. Also providing a much better framework than .Net that is also cross-platform could be implied as turning the tables against MS in its own game.

Thus we are stuck with the Mono it is today.
Now after hearing mine, what are your thoughts?


Edited 2009-01-12 15:43 UTC

Reply Parent Score: 0