Re: JVM vs .NET

In article <13ge8avfl581jd5@[EMAIL PROTECTED]
>, Jon Harrop
<jon@[EMAIL PROTECTED]
> wrote:
>
>I'm relatively new to both the JVM and .NET and am learning Scala and F#.
I
>was under the impression that .NET was essentially a later and greater
>reimplementation of the JVM in a Windows-specific form. However, I've
just
>discovered some nasty caveats in .NET.
>
>Specifically, if you generate and use regular expressions the obvious way
>then .NET leaks memory because it performs run-time compilation to
improve
>performance but fails to garbage collect the generated code when it is no
>longer needed. There are workarounds but I've yet to see a solution that
>can even garbage collect code under .NET properly, let alone an elegant
>solution.
>
>So I'm wondering what the JVM crowd have to say about the relative
>deficiencies of the JVM and .NET. Does the JVM garbage collect code
>correctly? Are there glaring flaws in the JVM?
>
>I'm aware of the array covariance problem in the JVM.
>
The JVM does a good job of garbage collecting, though 1 can write code
with 
memory leaks. At my previous company, our Java app servers ran 24 by 7 for
3 
months bewfore being bounced, and that was because we relased new
applications 
quarterly. This was on Solaris.

There is a 2 gig memory limit on Windows for a Java process. This is a
Windows 
constraint.

Eric