Interesting blog by Christian:

It's quite frequent that if I'm searching for some topic, whether on Google or DuckDuckGo or whatever, I often get very old, outdated results near the top. Recently I was searching for how the JAWS screen reader dealt with something specific to tables, and got the old Freedom Scientific page for JAWS 5. The current version of JAWS today is 13. I asked someone at a SE if there was a way to check the age of these pages and not let them get so high up (for thing that evolve quickly like languages and versions of software), and the reply was it's pretty difficult to tell programmatically what's outdated versus simply old (but still good).

SE's rely on things like how many links a page gets, and how often a page is referenced. The problem for things like Perl then is that the old crappy stuff gets referenced the most, which makes them sit near the top of results, which helps get them referenced more, endless cycle ensues.

For some of the Perl results, the results are old pages of current sites. Why not have BIG BLUE LINKS near the tops of these older pages to more updated versions? This steers people to better resources, which would get the newer pages referenced more, which would bring them up in SE's more, cycle continues in a better way.

But for the problem of no single, super-effective Perl tutorial: I'm not sure how one would get enough people involved. Unless it was higher-level tutorials over using stuff people happen to be using, like
howto CPAN
howto Elastic Search
howto (web framework here) <-- this area seems to be doing much better than general Perl stuff

One thing I hear PHP-lovers (and newbs) say is how great the PHP documentation is. I've never looked at it myself, so I don't know how exactly it's great, but can a bazillion newbs be wrong? Perl documentation that does right whatever does right.

The results I get in Google for "Perl Tutorials" is very likely NOT the same as what someone wholly new to Perl gets... because Google filters and I do visit : )