Slashdot Mirror
Mono 0.30 Released
Blair16 writes "From OSNews -- Mono 0.30 has been released. This release includes four components at once: the Runtime and Software Development Kit, the Documentation browser, and the ASP.NET server with its Apache module. Packages for various distributions are also available from our download page. This is mostly a fine-tuning release: bug fixing and performance improvements are the major benefits, but new classes and new features are also included. See the rest of the notes for details."
They're slow because they're still adding all of the bugs that VS.Net has already.
pb Reply or e-mail; don't vaguely moderate.
I thought I had Mono once for an entire year, turns out I was just really bored.
"Derp de derp."
What bugs? VS.NET is Microsofts most bug free application ever.
Seriously.
- Moomin
Sadly, the Debian packages are still in rather a strange state of limbo: You can get them if you can find the magic incantation to add to sources.list, but they're a January 14th snapshot (which isn't too old, but if you're going to do something from 2 weeks ago, why bother with a nightly snapshot in the first place, why not the last stable release?) and don't include libapache-mod-mono. Meanwhile libapache-mod-mono is also available separately but doesn't seem to work with the latest packages of everything else.
Which is making my attempts to port an ASP.NET application to work on mono a fairly frustrating experience, to say the least...
I have no idea why they decided on that name, but if mono comes from monoculture (as in the threat of a monoculture) i think it is a brilliant idea.
Meanwhile, Mono already has a complete suite of open source toolkits and APIs that run rings around what Microsoft offers and let any Gnome programmer become instantly productive on the platform.
.NET: both Java and .NET require open source programmers to learn completely new APIs, APIs that are arguably proprietary. And in the case of Java, there isn't even a credible attempt at an open source implementation (of, for example, Swing), and it is questionable whether an open source implementation is even legally possible.
.NET environment and Java support, to the degree legally possible.
In that, Mono has a leg up both on Java and on
Mono, in contrast, offers access to many open source APIs and libraries (foremost, Gtk+, which is the de-facto standard for Mono GUIs) and, in addition, makes a credible effort at providing a
Overall, the progress of the Mono project over the last year and a half has been nothing short of astounding. GNU C, GNU C++, and GNU gcj, took much longer just to produce a compiler and runtime, and all the open source Java platform efforts are woefully incomplete in comparison. The closest in terms of offering a complete environment is perhaps Python, but Python is a much simpler system under the hood and has different range of possible applications.
Haven't tried Mono, but i sure hope it is worth the change, from win32 .NET SDK, does anyone know about its performance, is it worth leaving my GNU C, for this MONO platform, or should i use C# for win32, when it comes to a *nix i stick with a C/C++ or a JAVA?
Now, I know that mcs is the compiler. I know that mono and mint run things ( but I don't know what the difference is ). I have no idea about the rest. I also don't know how to set up my "classpath". I am quite experienced in Java, but I am not sure how to go about using mono. Any hints would be welcome.
The ultimate goal is to get Piccolo.NET to run. Since I use the regular Java Piccolo all the time.
The only thing holding me back is the debugger which did not work well last time I tried (just usable, frequent lockups). Seems that it has been fixed, I'll give it a try...
The GNU Project is an open development initiative sponsored by Free Software Foundation and its contributors that is working to develop a free software version of the Open Group Single UNIX Specification development platform.
They may develop independant libraries, but the core of it is just implementing the Open Group's UNIX platform which is the core library. They will always be catching up in that initiative, and they might as well just develop a completely new base of libraries.
How about performance? Mono is of course still pretty young and has still a long way to go, but I think it is disastrous for Mono if Microsoft's performance stays ahead. .NET, and MS .NET is almost twice as fast as Mono. .NET Apps. Which one would you choose if you want to run your application? Just think of a weather simulation that might take one or two days to complete...
Just run the Scimark benchmark to see the difference. Java outperformes both Mono and MS
I think this performance issue is especially important due to the portability of
Face it, Miguel is a Microsoft stooge. This is about as opaque as the Soviet overthrow of the Afghanistan monoarchy.
How we know is more important than what we know.
That's gotta get ported. Use WINE or something.. just do it.
How we know is more important than what we know.
But why would anyone care if open source Java platform efforts are incomplete in comparison to Mono because complete closed source Java environments are readily available (at no cost) and are much better (performance, features, stability, general maturity, support, everything) than their Mono counterparts?
I'd advise everyone to stay away from Mono as Microsoft will screw the project somehow sooner or later (especially if they miraculously achieve some sort of portability between Windows and Mono).