As a bilingual Portuguese/English speaker who essentially spends most of his waking hours working in English but switching back when I leave my home office, I h

As a bilingual Portuguese/English speaker who essentially spends most of his waking hours working in English but switching back when I leave my home office, I have been very much annoyed by this since the dial-up days. Infuriatingly, there was a train of thought at one time that used website analytics as a justification for either setting the default language of a site or trusting an external third-party like IP addresses databases (often just relying on the free, unmaintained stuff that broke after 3 months as the Internet expanded). Then came the browser geolocation prompts, etc. -- and most people, lacking a basic understanding of how HTTP works, preferred chunks of JavaScript they could "see" to HTTP header information they didn't understand, to the point where that got codified as "best practice". It also doesn't help that most CMS frameworks completely fail to make use of that information and pass it down the stack, or that people have turned to doing SPAs (which _can_ just use navigator.language, but just do a search in any framework's source code and see how often that is used).