Beefy Boxes and Bandwidth Generously Provided by pair Networks
Your skill will accomplish
what the force of many cannot
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
I think that at the start of the Perl 6 project, the thought was that the community would have substantial input into the next version of Perl and may even take over the bulk of the development from Larry Wall and his small coterie; transform from the cathedral to the baazar in the design space, too.

It hasn't really worked out that way. Although there was a tremendous amount of input from the community in the form of suggestions for Perl6, it turned out that it is really hard to design a coherent language by community. So by universal acclimation, Larry once again became the lead designer and arbiter of good linguistic taste. Ironically, the perl6 community process has made more work for Larry, not less...

I don't see any major problems with the Perl community. But one could always suggest improvements.

One thing I would like to see is a site (or a section of Perlmonks) with an active community of module reviewers. CPAN is an embarassment of riches these days. Whether you want to multiply a matrix, create a template, parse a log, or train a neural network, there are multiple modules available and little information discussing their relative merits. Something like a Hitchhiker's Guide to CPAN would be useful in making sense of it all.

-Mark


In reply to Re: How would you rewrite perl community? by kvale
in thread Would you rewrite perl community? by Eyck

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others meditating upon the Monastery: (9)
As of 2024-04-23 08:33 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found