Slashdot Mirror


Mono Progress In the Past Year

Eugenia writes "OSNews posted an article accounting the applications created in GTK# the past 8 months, since the release of Mono 1.0. While many of them are still in their infancy, it's clear that the platform had a healthy progress, with 'super-hits' like Tomboy, F-spot, MonoDevelop, Muine & Blam! and other, less known gems, like SportsTracker, PolarViewer, MooTag, GFax, GIB, Sonance and Bluefunk. The 2.0 version of Mono is expected around May, but the developers advised distros and users to upgrade to Mono 1.1.4 despite being a beta."

5 of 441 comments (clear)

  1. Mono talk w/ icaza by camcorder · · Score: 5, Interesting

    Miguel de Icaza interview about mono on lug radio. Really nice one.

  2. C# Rocks - go mono go. by Tanaka · · Score: 5, Interesting

    I'm just getting into C#, and I love it. One interesting thing I found was that if I ran a socket server app on Windows, I couldn't connect more than 64 clients in a single thread. I tried the same binary on Linux/Mono, and it bombed out at 1011 connections.

    Keep up the good work - I'm loving it!

  3. C# is Better than Java(At least I think So) by Laoping · · Score: 5, Interesting

    Ok, Microsoft Is evil, this I will give you, but C# rocks. After years in C and C++, I moved to Java, and It was good, then about 2 years ago I moved to C# and it was better. Now I program in both, for work and graduate school. I have to say they are very similar, but when I am doing a program in Java, I always miss a few of the C# features (virtual keyword for functions, Get/Set are better in C#, etc)

    The only problem I have with C# was that it was not as portable as Java, but Mono came to my rescue. I was surprised how many of my program just worked in Mono (after removing winforms that is). I can't wait for version 2.0.

    Really, Mono should be embraced /.ers . If we can start making programs for the general population that run on *nix systems, but look just like they do on windows, more people will use *nix. What we have to realize is that most people in the world(not on this website J) don't have 4 computers in their basement running different operations systems, they just have the one running windows.

    P.S. And for some reason, they still have the sides on their computer case.......

  4. Re:it's not reverse engineering by beanlover · · Score: 5, Interesting

    Thank you for your post. I was one of those that believed because it was an ECMA standard that it was free and open.

    I went to the ecma site and saw this page:

    WARNINGS

    The liability and responsibility for the implementation of an Ecma Standard rests with the implementor, and not with Ecma.

    Below that was a warning and a linke about settling patent issues pertaining to ECMA standards. Scary.

    B

  5. Re:Did you forget about wxNET? by Coryoth · · Score: 5, Interesting

    Each platform has different HIGs which determine how an application should behave as well as how it should look. Using the same UI code on multiple platforms results in apps that don't match the HIGs on any platform except (if you're lucky) the one on which they were developed.

    Which raises the interesting question of whether we should be looking for another level of abstraction for GUIs beyond widget toolkits that let you write one codebase that then applies the HIG rules of the platform (which, of course, have to be something formally codified rather than just a spec document) to generate a (relatively speaking) HIG compliant UI.

    Imagine having applications written on a level such that the "OK/Cancel" button order is determined by the platform rather than by where the code explicitly placed the buttons. Such would certainly make GNOME and KDE much more compatible. At the same time it would formalise the HIG from a "reccomended way of doing things" into a mandated consistent GUI.

    Jedidiah.