You know nothing about San Onofre.

Waiting to hear "stories" would be of no use if, for example, attackers choose to wait until a nationwide cold-snap and then simultaneously brick one million thermostats.

The reason the FBI isn't doing more to combat revenge porn is thus: It's not illegal.
I would expect Franken, or at least someone who works for him, to know this. Perhaps he just wants it declared illegal by executive fiat, as is the practice with this administration.
But really, this ploy, and Slashdot's new social-justice-warrior driven coverage of it, is driven more by a desire to distract everyone from foreign events, Hillary's email server, and Obama's frequent and blatant power grabs.
That's actually kind of funny, now that I think of it. There's been no story posted at all about Clinton's email shenanigans. Well, we know who Dice has thrown their lot in with.

If there's a public safety concern about people hacking code in cars, then copyright is not the way to address it. The purpose of copyrights is purportedly to encourage the production of more works. It is certainly not intended to be a tool for ensuring public safety.

Ideally, hacking safety-related code (and then driving it on a public highway) should be legal only if the hacker got the appropriate certifications to work on that area, along with insurance riders to go with it. This would be completely unrelated to the copyright status of the original code.

Projectiles from your puny weapons will simply bounce off my armored playground robot.

Now, hand over your weapon and your lunch box to the machine.

Why compromise?

All the city bus drivers in my area are on video surveillance. We routinely get to see footage of accidents and altercations with crazed passengers on the local news.

If it's good enough for a bus, it should be good enough for someone responsible for the safety of a 500mph $200M machine.

Thank you for perpetuating the old joke that the Canadian national identity is based on Maple Syrup, Hockey, and 'not being America.'

It reverts to an incandescent bulb with an average lifetime of about 500ms.

Umm, that's why I originally said that languages should explicitly support both trapping and non-trapping versions.

Can anyone identify a product or service that Amazon doesn't sell or provide?

Job prospects are going to be few and far between if you leave Amazon.

In my defense, I did a google search before I posted. And I usually keep an eye on fark, though this week I've been busy.
Thank you for the actual links.
I do have a question for you- are you one of those sorts who finds every criticism of Obama to be coded racism?

The different flow of execution triggered by an overflow trap should almost always be a simple call to "abort()". At this point, your program has already failed and should be stopped.

I disagree with your premise. Garbage input values should be checked and rejected in software before the overflow ever occurs. The hardware overflow check should be a last resort to enforce this at every instruction step, and in the worst case it converts privilege exploits into less serious DOS attacks.

Allowing "garbage output" as you propose just creates more opportunities for attacks when that output gets consumed somewhere.

'5, Interesting' is a high score for bullshit.
I know you leftists hope and pray that every new mass murder is a right-wing terrorist attack. You must be constantly disappointed that nut jobs with leftist sympathies and Islamists are doing the actual killing.

On an X86, "V".

Not that checking it after every add instruction is really that practical. It would be better to have trapping and non-trapping versions of integer arithmetic, and to have languages with semantics which expose that choice to the programmer.

I'd like to invest in your fascinating scheme to sink $Trillions into needlessly duplicating infrastructure. Your concept of buying new 5X cost buried cables to compete with existing overhead wires just brilliant as well. Are you offering stock yet?