I'm reminded of the time when people said one wouldn't be able to survive speeds over 30 miles/hour in a train.

I'm reminded of the time when people were saying you wouldn't be able to drive more than 50 miles/hour in a car because the human reaction speed would be too low to be able to drive reliably at that speed.

People will adapt. Maybe it's not "our" generation that will be able to use this new technology. But that's not important.

In my opinion, Parrot assembly will replace C as a tool for development of programs that need to have speed. And languages based on the Parrot runtime engine, will replace all other languages out there, whether they're interpreted or compiled.

Perl 6, in my opinion, will be the language of choice for the future. But please remember, even to this day, people are maintaining programs developed in languages that are now over 40 years old. That's not going to change.

And I'm sure someone will create a module like YAPE::Regex::Explain for explaining Perl 6 code to us. ;-)

Liz


In reply to Re: Perl6 syntax being too much complex? How we will teach and read that?! by liz
in thread Perl6 syntax being too much complex? How we will teach and read that?! by gmpassos

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.