I didn't say anything about a requirement that it happen everywhere all at once, since I don't see any.
Do you use the same excuses when you write code that doesn't compile?
But automation *has* been delivering on that promise, and for some decades now. See upstream posts concerning gas jockeys and bank tellers for a couple of examples.
And what is the incentive for the people owning the machines to give away everything they make for nothing?
Not being torn limb from limb by a hungry, homeless, and angry mob.
Man, where's that +1, Troll moderation option when you need it?
Most people who want to eat can still find food.
Unicode is your friend.
Why do banks
A: You need to change banks.
My online banking allows me to block the use of my card to make in-store purchases or ATM withdrawals within and/or outside the country and/or EU. I can also enable or disable the use of my card for online purchases. I can also enable or disable any use of the card for other than logging into online banking from within the country--that last item takes a call to the bank. (Not sure whether not being able to lock yourself out unless you're overseas is a good or bad thing.) I can also set and change separate limits on in-store purchases, cash withdrawals, and online purchases. Doing any of these things takes about 2 minutes, and I can do any of them any time that it suits me.
Banking online with my bank also requires multiple factors--the card, a card reader issued by the bank, a government-issued personal ID number, and the PIN--and uses multiple challenge/response to confirm login and any monetary transactions, with a time limit of 4 minutes before the codes become invalid and you must start the authentication process over from scratch. I'm aware that there's no such thing as perfect security, but this seems to run pretty close.
Now you know why I quit reading Games of Thrones after the 3rd book or so, and why I've no interest in watching the series.
Another thing that bothered me is that the documentation consists mostly of examples. However, if I read documentation I don't want a code fragment to copy-paste, I want to read the specification for a particular method. In particular, how it handles edge cases. That information was usually missing. Of course you can test the behavior, but there is no guarantee the next release will have the same behavior if the behavior was never documented. All in all, it didn't feel like a good platform for writing reliable applications.
As someone who works on API documentation (no, nothing to do with
Skatteverket and I are on pretty good terms, thanks. Meanwhile, I suggest you check to see whether your sarcasm detector is plugged in.
Go back and read the comment I was responding to. Then read my response. Then ask yourself, "How did I manage so completely to fail to answer Zontar's question?"
I dream of a world in which Sony, on the sly, seeds a few torrents of the movie. Holy plausible deniability!
It'll never happen, of course...
"The true scholar prizes all drafts, early and late."