Now, for both you and Nico... ask yourself whether you (as a 'Hacker') are representative for 'most internet users in your country'. I think a website should be easiest in use for the biggest group of users.
As for me: I can get annoyed by behaviour like this but I'll always remind myself I'm not a 'regular internet user'.
As for most people I know: A lot have a dutch localization for windows and a dutch localization for Firefox/Chrome/IE. Quite a few (about 30%) have an english localization for their browsers (either because they have an english localization for windows or because they like 'consistent menus across all applications'.
I do agree with the author that geolocation should not be the first choice (cookies should be) but as a second choice it's better than the 'Accept-Language' header.
You are right, I'm probably not representative of most internet users in my country, but my OS and browser are in English, so it would be easy for Google to pick that up (or my cookies) and act accordingly, instead of redirecting me to the local version.
I don't think that works. Lots of people use a pirated OS. In Asia 99% of the people are using a pirated Windows, sometimes in English.
One of the software I've developed in the past auto-selects the user interface language based on Windows's own language. There had been at least one incident in which a customer complained about this; he was Filipino but was using a pirated Arabian Windows XP.
I'm all in for empowering the user too, but then again, it's all about the defaults.
In my experience power users find features like the 'change language button' a lot faster and easier than the average user. Even the tiny flags in the top-right corner of most websites go unnoticed for most people.
A 'regular internet user' doesn't even bother with the settings and/or is probably unaware of localization of search results. This doesn't mean she wouldn't get better results by searching without localization (assuming she's an english speaker).
What's worst is google for some reason changes back the settings to localized at what appear to be random intervals. The only definite working solution I've found is to use a US IP address to proxy from.
As for me: I can get annoyed by behaviour like this but I'll always remind myself I'm not a 'regular internet user'.
As for most people I know: A lot have a dutch localization for windows and a dutch localization for Firefox/Chrome/IE. Quite a few (about 30%) have an english localization for their browsers (either because they have an english localization for windows or because they like 'consistent menus across all applications'.
I do agree with the author that geolocation should not be the first choice (cookies should be) but as a second choice it's better than the 'Accept-Language' header.