Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Building a "useful Perl 6" 4 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • 1. If you need wiggle room, use Q2 2010. That's a part of why companies do it.

    2. Naming a release based on an injoke for a new language isn't very engaging or informative.

    • 1. If you need wiggle room, use Q2 2010. That's a part of why companies do it.

      "Spring" had a few other connotations that I liked for my purposes, but your point is well taken. After this week I'll likely just use a month to refer to the expected delivery date.

      2. Naming a release based on an injoke for a new language isn't very engaging or informative.

      * I think "Rakudo Star" probably has enough merits to stand on its own without the injoke.

      * It's really just a "working name" until/if we come up with one we like better.

      * I'm not sure that designations really need to be very informative at this stage -- we could've just said "Rakudo X" or "Rakudo n", but I personally find "Star" a bit more engaging than those.

      * I think it's least as engaging or informative as names like "Longhorn", "Dapper Drake", "Leopard", "Tiger", etc. Perhaps you disagree with those names also, but clearly there's already a precedence and tradition for this sort of thing by some well-respected organizations.

      Thanks!

      Pm

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.