The advantage to a project like Harmony, at least IMO, is to free an otherwise-acceptable langauge (Java) from the confines of a pretty stupid license granted by a pretty annoying company (Sun).

The Java standard, you see, is public. However, the reference implementation -- that is, Sun's JDK/JRE -- is only sorta-open. The goal of Harmony is to create a JVM that is free of the PITA license of Sun's JVM, and that could (for example) be packaged alongside Apache or an application.

The added motivation is that once such a huge task is complete, the OpenSource development model can take opportunities to improve its performance. Also, once the JVM is complete it could very easily be "ported into" projects like Tomcat, where an intimate level of integration could really improve the speed of servlets.

As far as the Java->Parrot converter, I suspect that's a bit easier, as it could require the extant JVM to be installed (along with the extensive class library) for the conversion process. No need to write all of that JVM code from scratch to do conversion.

The Eightfold Path: 'use warnings;', 'use strict;', 'use diagnostics;', perltidy, CGI or CGI::Simple, try the CPAN first, big modules and small scripts, test first.

In reply to Re: Parrot, Java, and Harmony by radiantmatrix
in thread Parrot, Java, and Harmony by dragonchild

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.