comment on

Let me put on my cranky implementor hat here.

Not a good idea, probably. The cranky hat doesn't look well with my ";)".

The "should" referred to my previous estimate, not to any reality. To clarify it further: in order for me to "win" my own "contest", it "should" have been released over a year ago.

I agree with most of what you say, am semi-active on perl6-language (oops, sorry), and donated to the fund (and plan on doing so again, repeatedly once every year, if I can afford it). I actively discuss Perl 6 on several fora and in general am very positive. I agree with the "released when ready" idea and prefer years of waiting to having a horribly implemented language. I may not agree with every decision made (things bothering me are ~~unicode~~non-ASCII operators, confusing use of the colon, overuse of the new french quoty qw, \d**{} and arbitrary limits like do-while), but I think Perl 6 is a really cool language. I do not mind that it is not released yet for I understand that quality takes time, and that implementation with an unfinished design leads to chaos.

Please, get rid of the cranky hat and re-read my post. This time, pay more attention to the ";)" and read the entire thread in the appropriate context: fun speculation. Or buy me a cranky head too, so that I can start a troll/flame war. It would be about something else, though, because debate is HARD when you actually agree with one another.

Juerd # { site => 'juerd.nl', plp_site => 'plp.juerd.nl', do_not_use => 'spamtrap' }

In reply to Re^3: Perl 6 release dates - two years later by Juerd
in thread Perl 6 release dates - two years later by Anonymous Monk

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Do you know where your variables are?
	PerlMonks