User login

Navigation

Contribute

Interested in contributing to FootNotes? Click here to submit news stories to us or visit this site for more information about available opportunities.

Art.GNOME.org

Error: It's not possible to reach RSS file...

GNOME Support

Friends of GNOME

Now's a good time to say thanks for the best desktop environment on the planet by becoming a Friend of GNOME or by upping your current Friends level. Contribute by joining the Friends of GNOME program. All contributions are tax-deductible in the U.S. Thanks to our generous Friends

Links of Interest

Syndicate

Mono Directions

Submitted by stro on Tue, 2005-11-22 09:08. 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

I have recently started to

Submitted by Anonymous George on Wed, 2005-11-23 05:01.

I have recently started to use mono for personal applications. This is my point of view:
- With mono, it is very easy and fast to develop a graphical application that works but eats lots of memory (mainly due to the philosophy of garbage collecting). However, after a little bit of code polishing, you can enormously reduce the footprint in memory, and even make it constant.
- With c/c++, you need much more time to develop an application that is prone to include memory leaks and other bugs. With much more time you can make it work flawlessly.

That's the choice. I think people wants FIRST to make pieces of code that works. THEN make them better. So, Java/Mono fits perfectly with that philosophy.

With respect to the speed, I don't really think that mono or Java (both with JIT compilers) are much slower than c++ as to be an issue (excep when the GC is collecting).

Personally, I think that the spirit under Java and Mono goes into the right direction. Can anybody imagine people today arguing whether programming in c/c++ is better than programming in assembler for common applications?... I hope no

» parent