Linked by Thom Holwerda on Sun 1st Apr 2007 21:56 UTC, submitted by suka
Novell and Ximian "Nat Friedman has been one of the driving forces behind the development of the Linux desktop for a few year now. First with his own company Ximian, founded together with Mono chief architect Miguel de Icaza, after its acquisition now inside Novell. A few months ago he has been named 'Technologist of the Year' by the VarBusiness magazine for his work around the SUSE Linux Enterprise Desktop. Since then he has been promoted to Chief Technology and Strategy Officer for Open Source, besides the desktop he is also overseeing Novells server business now. During Novells Brainshare Andreas Proschofsky had the possibility to sit down with Friedman and talk about the Linux desktop, the consequences of the Microsoft agreement and the mistakes of the Hula project."
Thread beginning with comment 226536
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Flamewars or Famewares
by SlackerJack on Mon 2nd Apr 2007 15:21 UTC in reply to "Flamewars or Famewares"
Member since:

Can you prove that mono apps are resource hungry as you claim?, i'm sorry but F-spot wipes the floor with most of it's kind.

Beagle only was resource hungry because of a memory bug which is fixed now. The funny thing is that the so called native versions of the mono apps only just have started coming out, just to prove a point maybe?

The whole mono thing has prompted C programmers to try and come up with a their version of the mono app always claiming it's faster/better.

Reply Parent Score: 1

dylansmrjones Member since:

The newest version ( of Beagle still takes around 50 Mbyte according to exmap. Tracker takes around 7 according to exmap.

Tracker uses much less memory, is much faster (you can especially feel it with Nautilus) and doesn't bug the system the same way as Beagle does, though Beagle continues to get fixes for deadlocks.

Beagle OTOH has a great GUI. But that's the one thing Beagle has going for it.

Reply Parent Score: 5

SlackerJack Member since:

Yes but is that because of mono or just bad coding?, C apps can do the same as well, bugs and memory leaks. Many C apps give a bigger memory footprint than others, so are you talking about mono or the application itself?

Reply Parent Score: 2

dylansmrjones Member since:

It is my belief it is a matter of bad coding. I have mono apps that loads in approximately .3 seconds (gedit takes 0.7 seconds). I have mono apps loading in 9 seconds.

I have C++ applications loading in .3 seconds and others takes 2.5-3.0 seconds. And eclipse takes 22 seconds. The only kind of applications that tend to take quite long on my system is Java applications. They are always slow to load, but quite fast after that.

It is not the language but the code - except for special situations (like directX in Windows - native C++ is much faster than .Net or mono).

Reply Parent Score: 2

RE[2]: Flamewars or Famewares
by moleskine on Mon 2nd Apr 2007 16:22 in reply to "RE: Flamewars or Famewares"
moleskine Member since:

Can you prove that mono apps are resource hungry as you claim?, i'm sorry but F-spot wipes the floor with most of it's kind.

No I can't prove it - can you? - but that was my strong impression over the past two or so years, particularly with SuSE's rug/zmd updater tool that didn't work properly. If the Mono Project is now getting to the stage of some fast, optimized apps, then good on them. However, this still begs the question of where reinventing the wheel is really going. Bringing Mono to the table takes cash and expertise that isn't then available for other, native projects. So I'd still question whether Novell is really on to a good thing - or a loser - by placing so much emphasis on it.

Reply Parent Score: 4