in reply to Re^3: Perl 6 is going to get a lot faster in 2013
in thread Perl 6 is going to get a lot faster in 2013

The real blocker to adoption is that perl 6 ain't yet complete.

What makes you think so? Do you have any data that supports your statement?

I ask because when we released the first version of the Rakudo Star distribution, we got loads of feedback. And most of it was along the lines of "the features are very nice, but it's too slow". Which indicates the the majority of potential users doesn't think that he lack of completeness is the main problem.

  • Comment on Re^4: Perl 6 is going to get a lot faster in 2013

Replies are listed 'Best First'.
Re^5: Perl 6 is going to get a lot faster in 2013
by Your Mother (Bishop) on Feb 04, 2013 at 18:28 UTC

    I agree with this. In my attempts to get on board it was speed and the dearth of documentation (and corresponding weakness in diagnostic feedback for misuse) that kept putting me back in the drink. I never considered "code completeness" for a moment; only "code what can I do with thisness."

      Documentation is still a weak point though a number of things were significantly improved in 2012. Most notably the new project has established the right architecture for a Perl 6 equivalent of Perl 5's perldoc.

      At least four big parts of the diagnostic feedback problem have been addressed in the last couple years:

      • The level of completion and stability of Rakudo. If there's an error, it's a lot more likely that the error is in the user's code not the compiler.
      • Error messages. Rakudo has finally caught up with Larry Wall's canonical STD parser. There's color coding, accurate pinpointing of where an error is, uncannily clever suggestions about what you meant to do, and so on. (Niecza was based on STD from the start.)
      • #perl6. The best way to learn Perl 6 is to get on the #perl6 freenode IRC channel and combine use of the on channel evalbots with questions. In watching #perl6 for the last year and a half I've seen a lot of newbies come ask questions and they invariably encounter patience and friendliness. Another great source for figuring Perl 6 out is to read the #perl6 log archive.
      • Rakudo source code debugger. A nice UI, debugging of regexes/grammars, debugging of exceptions, the works. And eminently hackable, too!
        Speaking of documentation, I was trying to figure out how to do some basic introspection stuff in the December release, and had no luck. Things like browsing through loaded modules/classes (keys %:: in Perl 5) and getting the current scope's variables (PadWalker), both useful for tab completion in the interpreter. Neither the regular nor the debugging interpreter seems to provide this information, and it looked like I might have to dig down into NQP or (shudder) Parrot to find it.

        Is there a Perl 6-level way to get at this that I missed?

      Slowness has been the major factor stopping me for getting into Perl 6 also.