Slashdot Mirror

← Back to Stories (view on slashdot.org)

Mono 1.0-beta3 Released

Posted by timothy on from the oneness dept.

steve_deobald writes "The Mono team just released Beta 3, the final beta before we see the 1.0 release candidate and final. Binary packages can be had for Red Hat, Fedora, and SuSE. Although not officially released, the new website is up and running. Also of note, MonoDevelop 0.4 was recently released, and has RPMs available for the first time."

4 of 38 comments (clear)

  1. Contrats to the Mono team by nelsonal · · Score: 4, Interesting

    A year ago in January I brought Mono up to MS execs who were talking about the portability of .NET (except to Linux) and they stated point blank that the project would never finish. Good on all of you.

    --
    Degaussing scares the bad magnetism out of the monitor and fills it with good karma.
    1. Re:Contrats to the Mono team by The+Bungi · · Score: 3, Interesting
      The core product groups never doubted for a second that Miguel would pull it off, mainly because Don Box and other architects working on .NET told them he would after they looked at the first alpha.

      There might be some "static" coming from the evangelism or strategy folks; I don't know. My perception of this is mostly positive.

      Microsoft, believe it or not, is happy (at least at that level) that Mono exists. There is nothing like having one of the main figures in open source sit down and implement a technology they opened. And I don't mean that with an evil or snickery undertone (and they don't, either) - they like it, just as they like all the SSCLI initiatives people have started to do since they released it.

      They've learned that you can be successful without closing up the specs, and those of us who write software for Windows for a living have benefited greatly from this.

      If Mono does nothing else it has already succeeded as far as I'm concerned. Microsoft has changed enormously since .NET was released.

  2. explain Mono by acomj · · Score: 4, Interesting

    I've visited the website..
    I can't figure out if mono is.

    1) A c# compiler? (bytecode??)
    2) A api library the is kinda like MS C# libraries
    3) An api library that had been developed from scratch.

    Or any combination of the above.

    Does it compile and run native or does it use bytecode like java?
    Can I build cross platform apps in it? (like java was supposed to be)

    I'm looking for a cross platform application building toolkit. I run OSX and linux.QT/GTK and C are some options I'm looking at, so far it looks like java/eclipse is the way I'm leaning, but this looked interesting and worth considering.

  3. I hate to say it by Anonymous Coward · · Score: 3, Interesting

    I see no measurable benefit of .NET vs J2EE. since I use and develop with both, I can say with all honesty it's a matter of preference. If someone wants to build GUI's but doesn't want to go to all the trouble of implementing custom tableModel, and treeModels, then .NET forms is easier. Of course that means your apps will look like everyone else's and reduces your competative advantage. If you prefer to code custom GUI's then you're better off using something like C++, QT, SWT or any other GUI package. On the serverside, I find .NET inadequate and the threading model inappropriate. Having to manually manage threads and constantly do callWait is not a good way to build scalable server applications. But that's from first hand experience. If I had to build server apps in .NET, I would rather do it C++ and not C#.