Linked by Eugenia Loli on Tue 19th Oct 2004 16:55 UTC
Mono Project This article provides a tour through some Mono programs, along with details about how you can start experimenting with them yourself. Not all of the programs featured here are finished products, but they're all exciting and show off interesting aspects of Mono. Even more Mono applications can be found at We should add to the list the excellent PolarViewer and SportTracker (they go together), and of course, GCursor#, CSBoardGalaxium Messenger, SkyNET and GLyrics among others like Bless, fewnn, GFax, WoodPusher, CDCollect and Kurush.
Permalink for comment
To read all comments associated with this story, please click here.
Python comments.
by Miguel de Icaza on Tue 19th Oct 2004 23:02 UTC

I should start by saying that Mono is language neutral, we
are an equal opportunity language runtime ;-)

I previously said that we could run .NET bytecode and
Java bytecode side by side. That is only a fraction of the
story. Mono through IronPython can also run most Python
code (except those modules that require a C extension).

IronPython is fairly mature, and passes the aggresive test
suite that Guido put together for the OSCON showdown this
year as well as the Python regression test suite.

So use the language that most pleases you.

That being said, there are comments along the lines of
`Python is not good for large projects'. I think that the
reality is much more complex that a short soundbyte, and
will largely depend on the kind of programs that you do,
the kind of programmers you have, the kind of timeline
that you are working from, the tools that you have at your
disposal and much more.

I think that Java and C# are particularly well suited for
doing component-based programming: they have a strong
focus on building component software, and by this I mean
that the language embodies things like accessibility to
the fields, methods, internals, strong on encapsulation and
mechanisms to extend these things.

The compiler is used as a tool to catch errors by using
static strong typing. Both Java and C# are moving to
even more strong typing with the introduction of Generics,
and this is a tool that can be used to catch more errors
in a project.

Some folks (and in particular large developer groups)
prefer to have compiler assisted type checking, other folks
do not. I think its a matter of taste and the scope
of your project.