Linked by Eugenia Loli-Queru on Sun 29th Jan 2006 00:13 UTC, submitted by anonymous
.NET (dotGNU too) A new version of DotGNU's Portable.NET and libjit (designed to be independent of any particular virtual machine bytecode format or language) has been released. There are a lot of new features, enhancements and bug fixes accompanying this release.
Thread beginning with comment 90740
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: How does this compare to Mono?
by calberto on Mon 30th Jan 2006 00:18 UTC in reply to "How does this compare to Mono?"
calberto
Member since:
2006-01-30

It would seem that Mono has had some fairly serious issues getting a quality VM/GC combination put together and it has suffered from some stability issues

I don't know what are you talking about (seriously). It's a little dangerous to put a comment like this, because you are not specifying teh exact problem you are suffering.

Anyway, Mono is not having those serious problems you are talking about, because the JIT runs fine (it could be tuned in some areas, but tha's taking some time, but there are people working on it). In the GC side, we are using the conservative Boehm GC, which has proved to be a very good solution in this area; observe, however, that a generational GC is going to be plugged in the nexts months (I don't know if that's going to be before or after the 1.2 release).

And I can't speak about the stability problems, specially because we have some arquitectures supported, so it could be habppening in one of them (at least x86 runs fine).

Hope it makes it clear (on the Mono side, becasue I don't know about pNet)

Carlos.

Reply Parent Bookmark Score: 1

jsight Member since:
2005-07-06

Yes, I know, my comment was a little dangerous. If I knew the system well enough to put all the details, I would have (and probably will post some to the mono list as I gain more experience with the platform). Having said that, here are my experiences:

1. I've used the system for a very limited time with a few simple ASP.Net applications and some client code (all managed). I've seen various crashes during the limited time testing on the platform that should not happen in a server application (took down XSP2 completely). One day, I'll take the time to get more details into the Mono bug database, in the mean time, I keep testing new releases.

2. GC -- The current one is non-compacting at the moment, which can lead to memory leaks through fragmentation. Hopefully the generational collector will fix this, but obviously it has not yet been released.

3. JIT -- Well, I didn't specifically mention this, as I've seen pretty good performance out of Mono generally. ;)

In any case, I do see steady improvement over there, and the code that I've seen in the class library is generally very well done.

Reply Parent Bookmark Score: 1