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.