Beyond the Perl 6 IRC channel, mailing lists and people attending hackathons. The software world has some 'perceptions' and defaulted semantics of terms release, production ready, complete, stable, usable etc. You can argue against it, but that is beyond the point. And explains my point regarding 'Marketing problems' we have. Lets say you go to a county, where they interchangeably call milk as water and water as milk. You know that is not true. You try to explain the whole country to correct themselves. But they are so much throughout generations trained to perceive them as such. The only option you have is to endlessly go on and correct the whole country(And they will never change) or 'change yourself'. The second option is better, because when you do that you begin to understand that they were actually right.

So lets try for a production ready release, which is as much production ready as much as Perl 5 is. Which I am pretty sure Perl 6 isn't today. Any thing other than that, and you are now going on a different plane. Moving the goal post, to ensure your goal counts is not how it should be done

Regarding Perl 6 being ready in an 'year or two', I take it for face value. Because reading the feature completion matrix once shows very few '-'s and there I believe 'its almost complete'. Regarding how much time remaining '-'s will take, we don't know. And even if they take little time, how many re writes it will take to get there is another question. And how many backends to which it will ported before those few '-'s are implemented is an another question.

So even though there are a few features left to complete, I doubt if rewrites, multiple backends and other stuff will allow you to get there in 2 years. Having said that even two years is a long time, and lot of things change in two years.


In reply to Re^9: Hockey Sticks by Anonymous Monk
in thread Hockey Sticks by raiph

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.