Skip navigation.

Mono Directions

Mono
Mono

Miguel de Icaza wrote:
We just released Mono 1.1.10, our best release so far. The major feature missing from this release to call it Mono 1.2 is the completion of our Windows.Forms implementation.

In this document I only present the direction of development of the Mono team at Novell; A more comprehensive view of other Mono developments by the Mono community is something that am working on and will post at a later date.

I also present how our team's priorities are shifting in response to Novell's own internal use of Mono and external factors like the final release of .NET 2.0.

Read the rest

Actually...

- One file per object (code or class) => hundred of file to handle, a real mess
Actually, I don't think that's a bad thing.

- Exception has to be catched. So your code is full of try part even if you don't want to handle the case.

Exceptions in C# and Java go right to heart of the work/academic argument. C# exceptions are designed with your average under pressure, working to a deadline, working things out as you go along coder. Java exceptions are designed with some academic goal in mind.

You *should* be catching all exceptions in perfect production code... but when you're developing software you are frequently trying things out and the very last thing you need is to be bugged by annoying exception errors all the time. Java goes out of its way to *stop* you from making any progress and is hugely frustrating. See the difference: Java, designed by academics with their platonic ideal of software development in mind. C# is Java that has been fixed by people who have to do real work knocking out code with a boss looking over their shoulder asking why it isn't finished yet. Microsoft may be a criminal monopoly, but they do understand how the real world of programming works... unlike the people behind Java.