I would ask whether those differences are from the language or the framework. I won't dispute that Microsoft produced frameworks that are better than a lot of the frameworks you find in the Java world. But the little bit of experience I have says that Java coded in a sane manner performs very well and has good memory usage properties. Not that I've looked, but I haven't seen anything indicating major difference between the raw performance of .NET and the JVM. And I know the JVM today is much, much better than it used to be.

Speaking personally when I'm forced away from Perl I'd prefer to go to Java than .NET. But that is due to disliking Microsoft, and not wanting to have any factor locking me in to any Microsoft platform.

In reply to Re^5: Perl and C# - how I use both by tilly
in thread Perl and C# - how I use both by jdrago_999

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.