I switched to DuckDuckGo primarily because google's results were becoming more frequently more frustrating and very often completely useless. The fact that DuckDuckGo has sane privacy features was "just" a huge added 'plus'.

Over a decade ago I realized that the single most important feature of a search engine is: Show results that match all of the search terms before showing any that only match some of them. The number two feature for me is to make it obvious where the line between "matches all" and "matches some" falls in the presented results.

Google spent a good decade following this maxim by virtue of only showing results that matched all search terms. Over that time, I've griped a lot about places that make this "classic rookie mistake" in regard to searching. CPAN is a great example of a place that does a truly horrid job when given more than one search term.

But several months ago, google decided to start silently throwing in results that only matched some of your search terms. This was not just "the last straw" for me atop the growing pile of steps google kept taking to pay less and less attention to what I actually asked them to search for. It was also a fundamental mistake that, as always, turned google into a frequently useless search service.

Yes, sometimes my DuckDuckGo search finds nothing and I fall back to another service. But for most other cases, DuckDuckGo gives better and often much better results than google. By searching DuckDuckGo first, I get both of my top features in a search engine. The obvious "line" is when I resort to google's much more numerous and much less selective list of results.

I thought PM linked to the https+html version but it is indeed currently linking to the http+html version. https+html seems a better choice to me as well.

- tye        

In reply to Re^3: Sometimes Perl is awesome: Duck Duck Go edition (google--) by tye
in thread Sometimes Perl is awesome: Duck Duck Go edition by educated_foo

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.