There are some traffic patterns where roundabouts don't do well. I've seen the following. Imagine a four way roundabout with north, east, south and west. Predominate rush hour traffic is towards the east. Heavy traffic entering from north. More entering from west. Most exiting at east with very little going around beyond west. Entering from south can be nearly impossible since they're waiting for a break from both north and west.
A relatively early type of mechanical telephone exchange was the rotary exchange [0]. The pulses from the phone cause a clutch to connect the rotary driver in the exchange which then moved the switching stuff around (details can probably be inferred from the linked article). One of the issues with the rotary exchange is the pads of the clutch wear, leading to unreliable connections. Aotearoa/NZ had an existing number plan when they decided to install rotary exchanges. Some bright spark knew of the wear issue, and calculated that, given the existing number plan, if they had the 1 position on the dial giving 9 pulses (etc.) then the overall wear on the pads would be much lower and so the maintenance requirement would be less. And that's where it started.
And another fun fact. I believe Norway chose the same configuration for their rotary phones. I'm not sure if it was for the same reason, though.
When friends started bringing pushbutton / cordless phones across from Australia, I was able to convert them to NZ numbering by reversing a few wires on the keyboard matrix. These generated pulses long before DTMF.
> they serve the same functional goal — input numbers
Well, yes and no. Same as how, when it comes to data types, it often has to be pointed out to inexperienced developers that a phone "number" isn't a number in the mathematical sense - you can't add or multiply 2 of them together to get anything meaningful. It's an identifying string, that happens to use only digit characters. "123" in a telephone number is three individual unrelated digits, whereas "123" in a calculator represents the number one hundred and twenty-three.
So the functional goal isn't exactly the same. One is entering individual characters, but on the other you're more likely to be thinking "one hundred and twenty-three" as you type its digits.
It may or may not be related to the actual reason for the inversion of layout, but the subtle difference felt like a (possibly minor) error in the initial premise.
Oh yes they do.
I saw a post on twitter about how game devs were using ChatGPT for localization and when you translated the text to English it said something like “as a chat assistant I’m unable to translate this concept” or an explanation instead of the translation.
This is exactly the sort of future I imagine with AI - not that the grunts on the ground will be sold on it but management will be convinced they can fire the people who know what they’re doing and replace them with interns armed with a ChatGPT subscription
http://news.bbc.co.uk/2/hi/7702913.stm