If the Perl community fragments into people answering questions in several different places, none of them will be good places to go to get information.

This is a pretty absurd claim. I don’t see how you can credibly make this slippery slope argument given the fragmentation that already exists. I read use.perl but hardly Perl Monks, these days. I picked up p5p a year ago, which I was never reading before. I have never posted on comp.lang.perl.misc. Presumably at least one of these places qualifies as a good place to get information in your opinion. If so, how is your position self-consistent?

I found Perlmonks via Google

Congratulations. Now, considering how many questions we get on Perl Monks from people who say “I know this is not Perl-related, but Perl Monks is the best place for this kind of thing that I’ve ever seen, so…”, how likely do you think are people new to Perl to ask Perl questions wherever they happen to already be regulars?

Knowledge forking is bad.

… why? What possible advantage does knowledge hoarding offer?

Experts don’t have unlimited hours to try to keep an eye on many different locations at once.

That is why you don’t want all the experts visiting only a single set of venues.

groups of people with few or no individual ideas that just parrot the loudest talking point currently in use.

The Perl community only sporadically pays attention to the hot issues of the rest of the programming world and almost never tries to sell its issues to a wider audience as worthy of attention, and the rest of the world happily ignores the Perl community. We’re pretty set in our ways, we know what works for us, and we are happy to leave it at that. If you don’t see that, or what’s wrong with it, then I don’t think I can help; an echo chamber never looks like one from the inside.

your new clubhouse.

If you think I care about Stack Overflow, you must not have read my posts. Another distraction is really the last thing I needed. But I care about Perl.

Makeshifts last the longest.


In reply to Re^4: Breaking Out of the Perl Echo Chamber: A Call to Action by Aristotle
in thread Breaking Out of the Perl Echo Chamber: A Call to Action by Aristotle

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



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.