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 343168
To read all comments associated with this story, please click here.
RE[3]: wow, i mean just wow....
by adkilla on Mon 12th Jan 2009 18:37 UTC in reply to "RE[2]: wow, i mean just wow...."
Member since:

From the vantage point of those who wish to see Mono as a purely multi-platform framework surely many are greatly disappointed in Mono. But Mono is an alternative implementation of .Net which at once is custom-tailored to both Linux (via Gtk#) and Mac (via cocoa#) and which on these platform provides very "native" applications(at least this is true for Linux and probably to a lesser extent for Mac-I don't have a Mac so I can't say much about the degree of Mono's success in making itself "native" on Mac) AND at the same time Mono is generic enough to make it cross-platform for a wide range of apps (server(Second Life) and client) on a trully impressive range of platforms (Wii, iphone, Android, Maemo etc.). You could fault them for trying to much, but not for not trying hard enough.

Some key points about Mono that I'll pull from from their FAQ to clear some misconceptions:
What is Mono™ exactly?

The Mono Project is an open development initiative sponsored by Novell to develop an open source, UNIX version of the Microsoft .NET development platform. Its objective is to enable UNIX developers to build and deploy cross-platform .NET Applications. The project implements various technologies developed by Microsoft that have now been submitted to the ECMA for standardization.

What is the difference between Mono and the .NET Initiative?

The ".NET Initiative" is a somewhat nebulous company-wide effort by Microsoft, one part of which is a cross-platform development framework. Mono is an implementation of the development framework, but not an implementation of anything else related to the .NET Initiative, such as Passport or software-as-a-service.

Aren't you just copying someone else's work?

We are interested in providing the best tools for programmers to develop applications for Free Operating Systems. We also want to help provide the interoperability that will allow those systems to fit in with other standards. For more background, read the Mono Project white paper.

More is available here:

I suspect that the decision against SWF had a bunch of factors. I think Mainsoft and the agreements between Mainsoft and Mono probably played a role in this. It is also possible that there were more patent concerns in this area and that MS had told them not to pursue this. And Miguel and his team have been privy to the planning of .Net far beyond what most .Net devs are and may have seen SWF as being but a short-lived tech which Microsoft itself would be leaving behind( I am not a .Net coder and no remarkably little about all the ins and outs but wasn't Avalon supposed to superced SWF ?-could be totally wrong but IIRC Miguel even mentioned this 2-3 years ago). At any rate I sill question the extent to which Mono could have created a multi-platform GUI which would not have been subject to derision by those who lament platform-specific integration. Java is only now becomming viable in this regard -people have bitched and moaned about Java being alien everywhere for so long-Java was practically forked for SWT to address this issue. Toolkits like Wx have only succeeded in addressing this issue to the extent that they have been successful and from my POV that success has been marginal. Qt seems to have the best cross-platform support-but there are issues there as well (licensing, costs, c++).

The #WT I mentioned earlier is a derivative of SWT. It did not require development completely from scratch.
If you have tracked the evolution of GUI toolkits, you may have noticed they have over time matured to fit in with the platform. Qt in its earlier incarnations was out of placed outside of Windows. But over time it has made design improvements and adapt itself even to GTK/GNOME L&F to better integrate with the DE. Qt has also improved so much on the Mac that an end-user of ours was hard pressed to weed it out as a non-Cocoa/Carbon app.
We've had the same experience with SWT. There is even a port of SWT underway for Cocoa64. Win64 support has been around for a long time.
While I agree there are GUI toolkit/frameworks that still have long ways to go (GTK on Windows/Mac and Swing on Windows), there are mature technologies to derive from.

As regards the exe/dll: I simply do not see this as being such a big issue. Firstly I suspect if Mono was ever to reach the point that people considered Mono before considering .Net (ie. Mono became the standard) that this could be changed-perhaps it should-but not when the number of Mono developers is dwarfed 100 to 1 by .Net developers. Secondly I have no clue as to what would be involved in creating a format which ran natively (ie. without ilrun and other mechanisms)-is such even doable? Now making Mono target ELF for Linux apps would make a lot of sense-but I suspect that lot of Mono development still takes place in MS Visual Studio-perhaps this plays a role in this decision-I really don't know-but you know I have never cringed seeing a dll file in my file system, and I have not gotten a rash due to seeing exe files. Mono apps are usually started with a bash script -big friggin deal-do you *really* care so much about whether Linux can make use of the RES chunk of the exe/dll file? I just don't get why this is a *deal-breaker*.

I am not disgusted by the sight of EXE/DLL, though I've had Linux admins that were confused that I sent them a Windows program for testing because of the EXE/DLL.

I was trying to point out that Mono applications could benefit more from native formats. For example, standard system tools like ldd are especially beneficial in cases where trouble shooting runtime dependencies are needed. This is doable just not done currently. Under Windows the Dependency Viewer provides similar functionality for Win32/Win64 native binaries. This includes .Net apps and assemblies as well. Using ldd in this manner could not happen under Linux unless the ELF binary is used.

I guess my last question is this: you seem to be quite competent in .Net programming- what is preventing *you* from offering your skills to implement the things you so wish to see ? I am not currently an active programmer and I would need to invest an awful lot of time and energy to be able to even be able to code something more than hello-world in c#, but then again I am not lambasting Mono for it's shortcommings -au contraire I thank the Mono team and devs for their work

From past experiences in OSS projects, I've learnt that it is key for a project to have firm supporters and stick with a clear goal. #WT was one of the biggest disappointment for me personally as I saw my contributions fall to wayside and the direction the Mono folks took instead. The original SharpDevelop team that sparked of #WT decided it was best to lay the project to rest and instead focus on consuming S.W.F. Lessons were learnt and I moved on to alternatives.


Reply Parent Score: 1