Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
I don't demand anything, except honesty. I do retain the right to criticise people, volunteers or otherwise, who don't follow through on their promises. Lies aren't acceptable to many people.

People who say they're going to do something, and then don't do it, disappoint others. Obviously the people who planned to address problems and then chose not to disappointed a lot of people, self included.

People coming into the Perl community should know that history, and know that coding with perl isn't all the sunshine and roses that it's portrayed to be by it's breathless enthusisasts. They shouldn't believe promises that the documentation will be cleaned up "real soon now", because that's been false for a long time now. Those promises are still in the documentation; and they're still lies.

There are issues for and against perl, and in this thread, perl's documentation was being presented as a strength. I felt it was only right to point out the weaknesses, as well; and to prevent others from being mislead by false promises, like I was in thhe past.

Perl can do good work. It could be better if it were better documented. People in the Perl community complain that they want more supporters and perl enthusiasts, and write long threads wondering how to attract people, but they don't want to do the basics, like document the language cleanly, simply and concisely. Now, I'll make a prediction: your response (if you respond at all) is going to be even less relevant and coherent than your original rant. This is Ad hominem, antagonistic, and completely uncalled for! I'm not "shooting" at you; I'm providing a valid criticism of an otherwise useful language, based upon real world experience. So go ahead, give me your best shot, but I'm not going to be surprised. Nor open minded... it seems. I'm only replying for the benefit of those who might be misled by all the Perl cheerleading, not for your empty minded, selfish complaints. As for you, get lost. No one need empty minded boosterism.

In reply to Re^3: How I started reading Perl's (builtin) documentation. by Anonymous Monk
in thread How I started reading Perl's (builtin) documentation. by techcode

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, 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, 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.
  • Log In?

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

    How do I use this? | Other CB clients
    Other Users?
    Others wandering the Monastery: (7)
    As of 2020-05-30 19:26 GMT
    Find Nodes?
      Voting Booth?
      If programming languages were movie genres, Perl would be:

      Results (173 votes). Check out past polls.