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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Give some thought to forward compatability. People will be much more likely to use "Rakudo Star" for real-world applications if they can be guaranteed that the version of the language they're writing to will remain supported after the language evolves in future releases. If upgrading Rakudo will break real-world applications because the language semantics evolved, that will discourage anyone from writing those applications in the first place, especially serious ones that can't necessarily be rewritten every time the language evolves...
    --

    Deven

    "Simple things should be simple, and complex things should be possible." - Alan Kay

    • I think you're addressing the more practical nature of Perl 6 which still seems premature, as I read this thread. There are applications to be written, libraries to be ported, packages to be bundled, books to be written, training classes to be prepared. Until it syntax/semantics are stable (not necessarily code stable) then it's pretty much impractical to do most of these things. And some have *long* lead-times (books, porting projects). Some can't be undone (releasing an app into the wild). Software h
      • So, riddle me this. What would an adult prefer: shoehorning all software projects into a 6 stage development model, or looking at the dynamics of a community and trying to find a development model that works well and produces the best result? Your stages are mighty fine for a lot of situations, but I'd hate to be as inflexible to think it's the only way to succeed.