Slashdot Mirror

← Back to Stories (view on slashdot.org)

Mono 0.30 Released

Posted by michael on from the still-a-terrible-name dept.

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."

4 of 32 comments (clear)

  1. Re:I can see the ad campaign now... by MBoffin · · Score: 4, Informative
    You would that instead of perpetually being behind Microsoft in the current state of the libraries, that we would develop a completely new set of libraries. That way we aren't always playing catch up to what will ultimately be a windows only set of libraries.

    The Mono project is developing its own set of libraries. Read Question #1 of the Mono FAQ. This is why I support the Mono project. It's not just following in the footsteps of Microsoft. It's taking a good idea and pushing it beyond where Microsoft may or may not choose to take it.
  2. Re:Holding out for debs by reaper20 · · Score: 2, Informative

    They were in incoming earlier today and are already on my debian mirror.

    They're still the January 14th CVS pulls, but at least they're in Sid now, along with gnome-sharp and gtk-sharp, so they're probably packaging .30 as we speak.

  3. Re:Can someone explain it all to me? by Anonymous Coward · · Score: 3, Informative

    mint - interpreter which is easier to port to different architectures but slower than mono

    mono - JIT runtime (faster than mint)

    monodis - disassembles assemblies (.exe and .dll) to CIL bytecode

    mcs - C# compiler

    example:
    mcs file.cs -o file.exe
    mono file.exe

  4. Mono performance by Anonymous Coward · · Score: 1, Informative

    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.
    Just run the Scimark benchmark to see the difference. Java outperformes both Mono and MS .NET, and MS .NET is almost twice as fast as Mono.
    I think this performance issue is especially important due to the portability of .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...