Its also bullshit on iOS 9.2.1.
That's the clever thing about the story; nobody will be willing to check it.
On the other hand, it has been reported that the problem isn't setting the time to Midnight Jan 1st 1970. The problem is setting that time for example in the USA, because in the USA you set the time to some hours _earlier_ in UTC. And these reports say that the problem fixes itself when the time goes into positive time UTC (in Los Angeles you might have to wait nine hours). And _I_ am not going to check if this is true.
Or some idiot drives into a lake or down a jogging trail because he or she is just TOO STUPID to understand that they're not driving on a road anymore.
I once was told by my SatNav to drive into a lake. There is a lake, an island in the lake with a major tourist attraction, a ferry, and the road goes straight to the like so you can drive onto the ferry (and you need to have some good reason to do so because car traffic is normally not allowed on that island).
I actually drove past the car park 150m away from the lake before I spotted the end of the road. In the dark you could easily drive into the lake without being a complete idiot (a bit stupid and careless, but not a complete idiot).
For YEARS, I've hoped for GPS software that had three features:
4. Find a petrol station along my way with the smallest possible detour. TomTom finds the nearest, but that might be two miles away which means four miles detour. But 20 miles further there might be one just along the way.
5. Find the "cheapest" route, taking into account wear on the car, fuel, and my time.
This basically means that you just need one arbitrary code execution vulnerability in Firefox and it's game over. In contrast, if you have the same in Chrome, Edge, or Safari, then it's just the first step - you now have an environment where you can run arbitrary exploit code, but you can't make (most) system calls and you have to find another exploit to escape from the sandbox. Typical Chrome compromises are the result of chaining half a dozen vulnerabilities together.
but it was fully backwards compatible with GW-Basic
No it wasn't. I had to install GWBASIC separately from a DOS 4 install disk after upgrading to DOS 5, because the Chain Reaction GWBASIC game didn't work with QBASIC.
Robots don't feel those emotions, and have committed no massacres on that scale. I trust robots more than I trust humans.
Do you trust a gun? Do you trust a bomb? Of course not, because the concept is meaningless: neither will cause harm without instructions from a human. Both can magnify the amount of harm that a human can do. Autonomous weapons, of which landmines are the simplest possible case, expand both the quantity that a person can do harm and the time over which they can do it.
During the cold war, there were at least two incidents where humans refused to follow legitimate orders to launch nuclear weapons - in either case, the likely outcome of following the orders would have been the deaths of many millions. The worst atrocities of the second world war were caused by people 'just following orders'. And you think that it's a good idea to remove the part of the chain of command capable of disobeying orders.
Writing software is more fun than working.