That was mostly PSF's fault since they had the default documentation URLs setup to point at the Python 2 documentation for way longer than they should have...
Ha, me too, but then I've also been caught out on 'latest' (which I typically reflexively click on after opening) having some crucial difference from what we're using (12 vs. 13) too, so hard to win there.
I don't know off-hand if it's possible with the search (e.g. it might use a last-selected version cookie) but we should probably be using version-specific 'bangs'. `!pg12` or whatever, in my case.
So does Google, and it’s even worse there. In Google, the first page for "postgres window functions" is version 9.1, version 9.3, and 8 random tutorials. DDG has 9.1, 9.3, tutorial (the same as Google…), but then you at least get 12, 11, and then some more tutorials.
Comments
I use duckduckgo and it always finds me PostgreSQL documentation for version 9.3 or 8.x or something obsolete like that during general search.
Google gave me Python 2 results for every doc query for a looooooonnnnnngggg time, I just clicked to the newest version when I got there.
That was mostly PSF's fault since they had the default documentation URLs setup to point at the Python 2 documentation for way longer than they should have...
Oh really? Interesting. I always thought it was because Google never switched to Python 3.
Ha, me too, but then I've also been caught out on 'latest' (which I typically reflexively click on after opening) having some crucial difference from what we're using (12 vs. 13) too, so hard to win there.
I don't know off-hand if it's possible with the search (e.g. it might use a last-selected version cookie) but we should probably be using version-specific 'bangs'. `!pg12` or whatever, in my case.
So does Google, and it’s even worse there. In Google, the first page for "postgres window functions" is version 9.1, version 9.3, and 8 random tutorials. DDG has 9.1, 9.3, tutorial (the same as Google…), but then you at least get 12, 11, and then some more tutorials.