I'm just going to throw in some thoughts about some questions.
What does that mean some languages are dynamic ?
Like many things, there isn't a clear cut definition. But typically, languages for which the types of all the variables are always determined at compile time are called "static". C and Java for instance. In dynamic languages it is possible that the types of variables are only determined at run time. Or that it's more values that are typed instead of variables (one could easily few Perl5 that way). Perl6 will be dynamic. While it is possible that the types of Perl6 variables are determined at compile time, the programmer isn't forced to reveal them (and hence they aren't know till runtime). In dynamic languages it's usually easier to load in new (source) code during runtime.
What are the business advantages of using dynamic languages?
That is not the same question as "Why is it good for a business (hi-tech or industry) to use a dynamic language?" Just because there are advantages of using a dynamic language doesn't mean that using a dynamic language is good for a business. There are also drawbacks of using dynamic languages (if there weren't, everyone would use dynamic languages). What language a business should use for a project will depend on the project - and the business. In-house expertise is a non-significant factor in deciding which language to use.
What is the acceptance level of Parrot outside the Perl6 community?
You write: Some percentage of Perl5 people seem to have reservations about Perl6 and then probably also about Ponie/Parrot. You seem to imply that people who have reservations about Perl6 necessarely have them against Ponie or Parrot as well. That's not true. Parrot will give use features totally independent from Perl6 (in fact, that's what Ponie is doing...). Perl6 is a change of the language - Parrot is a change of the implementation. The language could have changed without creating Parrot. Parrot could have been done without Perl6. I've heard many voices questioning Perl6 in one way or another. But I haven't heard anything against Parrot.
What are the benefits for those other languages to use Parrot?
Will Zend use Parrot for PHP? Does it matter? Making Parrot the main vehicle for other languages isn't its primary goal. Parrot will be a general purpose VM geared towards dynamic languages and Perl6 in particular. Being able to run PHP on Parrot means it's easier to interface PHP and Perl code. But a implementation specifically created for PHP (or whatever language) is likely to be "better" for that language than Parrot. For some definition of better (speed, memory footprint, portability).

Would using Parrot for Python hurt the Python community? Did JPython hurt the Python community? And again, being able to run Python on Parrot doesn't mean Parrot becomes "the" vehicle for Python. It just means it's "a" vehicle for Python.

When is it going to be available?
Sure, we don't have a dead-line for Parrot or Perl6 and I think the answer should be NOW. Well, it is available now. Just go to dev.perl.org and download what's there. But I wouldn't want to use it as it's far, far from complete.

Will code written today run on Parrot? It depends what code you mean. Yeah, there are promises that Perl5 code will run under Perl6/Parrot. But that's just a promise for *Perl* code. Not XS. XS code won't run on Parrot.

Sure, Ponie promises Perl5 compatibility. Hmmm, yeah, Ponie. If I go to www.poniecode.org, there isn't much more than a press release of a year and a half ago, and after some more clicking, one quite old download. Is anything actually going on with Ponie?


In reply to Re: Parrot, the future of dynamic languages ? by Anonymous Monk
in thread Parrot, the future of dynamic languages ? by szabgab

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.