Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer
 
PerlMonks  

Re^4: A $dayjob Perl 6 program that runs 40x faster on the JVM than on Parrot

by raiph (Hermit)
on Aug 04, 2013 at 20:15 UTC ( #1047824=note: print w/ replies, xml ) Need Help??


in reply to Re^3: A $dayjob Perl 6 program that runs 40x faster on the JVM than on Parrot
in thread A $dayjob Perl 6 program that runs 40x faster on the JVM than on Parrot

my opinion really isn't the primary driver of language adoption

My interest is trying to encourage contribution not adoption. (I've always thought adoption will largely take care of itself and will reflect how robust the product is.)

People are avoiding Rakudo because P6 hasn't delivered anything useful and usable for general consumption in thirteen years.

By mid 2003 people were avoiding Mozilla because it hadn't produced anything useful and usable for general consumption despite spending many millions of dollars and 6 years on it. Because I knew what was going on behind the scenes, I chose to continue to contribute and try to attract more contributors in the face of ill-informed ridicule and attacks. The same applies to Perl 6.

sane socket support?

sri's issue is non-blocking sockets which depends on using the underlying VM's support for concurrency. As labster said less than a week ago, the current short term plan is "get the JVM working ... start getting threads flushed out ... then buffers, and sockets". As things stand right now the JVM is sufficiently working, some initial concurrency primitives including threads have been implemented (more have arrived since that commit), jnthn made a series of improvements to the Buf type just before leaving for a week vacation, and today, his first day since returning, he's begun making socket commits.

documentation that wasn't a pile of specification tests hyperlinked to synopses under constant churn

See Perl 6 documentation.

keeping a working ecosystem might let people get things done

People manage to get things done.

Module breakage is generally relative to git head, not Rakudo Star (the quarterly batteries included distribution which is what users wanting stability should use).

#perl6 is typically very responsive to any regressions brought to their attention by a user.

Head is developing rapidly. So there's often a lot of breakage against head. This has reached an all time peak in the last few weeks.


Comment on Re^4: A $dayjob Perl 6 program that runs 40x faster on the JVM than on Parrot
Basic Literacy for P6 Advocates
by chromatic (Archbishop) on Aug 04, 2013 at 20:26 UTC
    I chose to continue to contribute and try to attract more contributors in the face of ill-informed ridicule and attacks.

    I stopped contributing because I was tired of people talking about how good things were surely going to be in the very near future and then doing almost nothing to make them happen. You're keeping up a fine and well established tradition here of making big promises based on things people say.

    See Perl 6 documentation.

    Keep telling yourself that a series of blogs, example mathematical puzzles, and Larry promising that this year for sure he'll write a book (he's been saying that since 2005) are acceptable forms of documentation that people like me want. (They aren't.)

    I've always thought adoption will largely take care of itself and will reflect how robust the product is.

    Finally, we agree on something.

      Keep telling yourself that a series of blogs, example mathematical puzzles, and Larry promising that this year for sure he'll write a book (he's been saying that since 2005) are acceptable forms of documentation that people like me want. (They aren't.)

      You suggested that the only documentation was "a pile of specification tests hyperlinked to synopses under constant churn". That comment ignored the doc.perl6.org project and the above follow up does so again.

      You do Rosettacode a great disservice, and mislead monks, when you suggest that it's just mathematical puzzles. The 679 programming tasks cover any programming task contributors have chosen to contribute. It only takes a quick glance to see that most of them are things like basic and advanced programming techniques, file, string, Unicode, and date manipulation, and so on. (There are Perl 6 solutions for over 600 of them.)

      (Edit: removed comment about Larry, and simplified initial paragraph.)

        The so-called Perl6 documentation is a very sore point. Recently my boss tried to look at Perl 6, but all of the human-readable documentation he could find as an outsider assumed that he was already fluent in Perl 5. This is quite bad, as it prevents people who do not know Perl 5 from ever learning Perl 6, unless they take the detour through Perl 5.

        I don't know what to make of the linked http://doc.perl6.org/ - it feels to me like some automatically generated documentation that is not intended for human consumption. Maybe it is a good reference if you're looking for a concise description of how an operator works, but it surely can't be intended as the starting point for getting in touch with Perl 6.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1047824]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others studying the Monastery: (11)
As of 2014-12-26 14:35 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    Is guessing a good strategy for surviving in the IT business?





    Results (171 votes), past polls