Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options
 
PerlMonks  

Re: perlcheat

by ghenry (Vicar)
on May 06, 2005 at 14:09 UTC ( #454683=note: print w/ replies, xml ) Need Help??


in reply to perlcheat

Could we add http://perldoc.perl.org to the list of urls?

Thanks.

Walking the road to enlightenment... I found a penguin and a camel on the way.....
Fancy a yourname@perl.me.uk? Just ask!!!


Comment on Re: perlcheat
Re^2: perlcheat
by Juerd (Abbot) on May 07, 2005 at 00:24 UTC

    Could we add http://perldoc.perl.org to the list of urls?

    No, there's no room for a very long URL like that. The only URLs that are unimportant enough to go are tpj.com and perldoc.com, both too short to be replaced with perldoc.perl.org. It should be perl.org/doc or doc.perl.org anyway, and not have "perl" twice in the URL. (The reason for using perldoc in full was Google ranking. I don't agree with optimizing for search engines either.)

    Juerd # { site => 'juerd.nl', plp_site => 'plp.juerd.nl', do_not_use => 'spamtrap' }

      Well, OK. But I don't think it's that long a url.

      I also think the reason it's perldoc.perl.org and not doc.perl.org, is that the previous url was perldoc.perldrunks.org and nothing to do with Google ranking. I may be wrong however.

      Gavin.

      Walking the road to enlightenment... I found a penguin and a camel on the way.....
      Fancy a yourname@perl.me.uk? Just ask!!!

        But I don't think it's that long a url.

        For perlcheat, it doesn't matter how long a URL feels, or what you think is appropriate. It's about number of characters and what will fit, and what will not.

        I also think the reason it's perldoc.perl.org and not doc.perl.org, is that the previous url was perldoc.perldrunks.org and nothing to do with Google ranking. I may be wrong however.

        I can't find the specific message, but I was told that "perldoc" had to be in the url, as a whole, to get a greater chance of getting to perldoc.perl.org if someone googles for "perldoc perlop".

        Juerd # { site => 'juerd.nl', plp_site => 'plp.juerd.nl', do_not_use => 'spamtrap' }

      It should be perl.org/doc or doc.perl.org anyway, and not have "perl" twice in the URL.
      Does it also bother you that every perldoc about perl has perl in it's name? For example, perlreftut, perlfunc, perlsec... That is to say, that the perldoc already says that we're looking at the documentation for perl, why prefix the subject with perl again?

      thor

      Feel the white light, the light within
      Be your own disciple, fan the sparks of will
      For all of us waiting, your kingdom will come

        Does it also bother you that every perldoc about perl has perl in it's name? For example, perlreftut, perlfunc, perlsec... That is to say, that the perldoc already says that we're looking at the documentation for perl, why prefix the subject with perl again?

        Well, that the documents have "perl" in their name is useful, because POD isn't specific to Perl, and the documents are made available for man too, where clashing with other documents must be avoided.

        That I have to *type* "perl" twice is stupid. And yes, that bothers me. "perldoc op" should just display perlop as long as there is no op.pm, and when someone creates op.pm, they're doing something wildly incorrect.

        For the URL as visited by machines or people who click links, the redundancy and length are no problem. In fact, I agree that for recogniseability, it's useful. But for those who *type* URLs, the URLs are of annoying redundancy and length. People who hang out on IRC type URLs all the time, to help people find the right documentation. That's why I created http://tnx.nl/404, which redirects requests like http://tnx.nl/op to the appropriate page.

        It sucks that this is done with tnx.nl, which is unofficial and a weird name. But it's short. "tnx.nl/op" is much shorter than "perldoc.perl.org/perlop.html". That's three times "perl" and a ".html" that nobody visiting the site should have to care about. But Ask has his reasons to not want this for perl.org. In this area, PHP takes the lead, with its http://php.net/function URLs.

        Juerd # { site => 'juerd.nl', plp_site => 'plp.juerd.nl', do_not_use => 'spamtrap' }

Log In?
Username:
Password:

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

How do I use this? | Other CB clients
Other Users?
Others meditating upon the Monastery: (12)
As of 2014-10-23 18:50 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    For retirement, I am banking on:










    Results (128 votes), past polls