It seems I'll have a chance on Wednesday (22 December) to give a 20-30 minute talk infront of a few hundred IT managers with the title Parrot, the future of dynamic languages. I just don't yet know what am I going to say....

I'd appreciate to read your thoughts.
I was thinking about questions such as

• What does that mean some languages are dynamic ?
  ActiveState has a good white paper on dynamic languages. But what do you ppl. think ?
• What are the business advantages of using dynamic languages ?
  Why is it good for a business (hi-tech or industry) to use a dynamic language ?
• In what fields do the dynamic languages fit better than Java/.NET etc. ?
  I could just say they are better than Java, C#, COBOL and VBScript but first of all VBScript is I also in the dynamic category and besides such overall claim nevr works. And is not true either.
• What is Parrot?
  And more importantly, how will that impact the dynamics of the dynamic languages ?
• What is the acceptance level of Parrot outside the Perl6 community ?
  Some percentage of Perl5 people seem to have reservations about Perl6 and then probably also about Ponie/Parrot. Further more, what do we know about Python, PHP, Ruby, Tcl and other language communities ? How do they see Parrot ?
  I know I should ask this on forums of the respective communities too.
• What are the benefits for those other languages to use Parrot ?
  The question is interesting both technically and business wise. E.g. Will Zend use Parrot for PHP ? Would using Parrot for Python hurt the Python community ?
• 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. But this brings up the question of migration. Will code written today run on Parrot ? Sure, Ponie promises Perl5 compatibility. What about the other languages ?

So, what should I say about the above ? What else should I talk about ?
Your input is really appreciated.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.