News for hackers. Stuff that matters.
Re:Rust is mostly safety by jMyles on Thursday December 29, 2016 @08:24AM (#13277107)
> countless lives lost

I have no doubt that people have had their lives ruined, or even died, as the result of flaws in system programming, but is anyone actually tracking this? Is it "countless?"

Re:Rust is mostly safety by IgorPartola on Thursday December 29, 2016 @09:54AM (#13277541)
No. Nobody is counting. That's why the OP said countless.

"What have you done? That vase was priceless!"

"Oh good, I was afraid it was expensive."

Re:Rust is mostly safety by 010a on Thursday December 29, 2016 @10:07AM (#13277625)
While that's a funny definition of the word, technically speaking the word "countless" does mean "too many to count".
Re:Rust is mostly safety by bassislife on Thursday December 29, 2016 @11:14AM (#13278089)
I think it was humor :)
Re:Rust is mostly safety by psyc on Thursday December 29, 2016 @11:58AM (#13278379)
TDD: "If you're not doing this, you're not a real engineer."

Rust: "If you're not doing this, you're a murderer."

Re:Rust is mostly safety by lotyrin on Thursday December 29, 2016 @01:49PM (#13279142)
I'd really like to see an organization when evaluating tools or practices, do an actual risk assessment even just once. Even a hand-wavy conversation where we make 0th-order number-of-zeros estimates on any of the quantities involved in making such a decision.

I'm a huge fan of thorough designs, engineering formalities and quantifying application performance, but if we're building some fast food ordering app is expected to increase sales by 10 percent as soon as it's done and there's no risk from quality or availability or performance of the application (other than the 10 percent extra sales, we expect people to walk in / drive thru like normal if it under-performs on those metrics) then it's obvious the business value is in launching a minimal implementation as soon as possible using tools that optimize for productivity, not safety or performance.

Too often I see dogmatic pure functional TDD line of business app with continuous deployment infrastructure that could break for two weeks at a time without impacting anyone, or the copy-pasted-code-from-google-searches business-critical application that loses money for every hour it's offline but has no software development lifecycle or monitoring or alerting or anything.

Re:Rust is mostly safety by sidlls on Thursday December 29, 2016 @04:04PM (#13280116)
Yep. That may not be the intention but it certainly comes off that way.
Re:Rust is mostly safety by ragebol on Thursday December 29, 2016 @08:28AM (#13277125)
Well, if no one is tracking it, there is no count and that would thus be countless.

But in all seriousness, I am curious about this as well.

Re:Rust is mostly safety by moxious on Thursday December 29, 2016 @09:48AM (#13277501)
It's not "countless" it's "uncountable" because we couldn't agree on what a software caused death was.

In my CS program we had an ethics class that included stories of bad X-ray machine software that overdosed people. Bad, bad bad. I don't think many people died as a direct result, but 10 years later there was probably a spiked cancer incidence. Did software kill people? Well yeah....kinda.

In airplane systems, there have been a number of cases where bad alerting / warning systems basically either misled the pilot or lulled them into a false sense of security prior to events that caused crashes. Did software kill people? Uhm, yes, I think, sort of, but not directly?

It's only when we get fully sentient AI that arms itself and decides to clean up the human pestilence that we'll be able to draw a straight line there. :)

Re:Rust is mostly safety by 1wd on Thursday December 29, 2016 @10:35AM (#13277804)
Errors in the software of the radiation therapy machine Therac-25 directly lead to the death or serious injury of six patients. Three patients died within weeks or months. http://radonc.wdfiles.com/local--files/radiation-accident-th...

Errors in the software of a MIM-104 Patriot resulted in failure to locate and intercept an incoming missile and the death of 28 soldiers. http://www.gao.gov/products/IMTEC-92-26

Errors in the software of a Chinook helicopter may have lead to a crash that killed 29 people. http://www.publications.parliament.uk/pa/ld200102/ldselect/l...

Errors in the software of Toyota's throttle control system may have lead to the death of 89 people. https://betterembsw.blogspot.ch/2014/09/a-case-study-of-toyo...

More: http://www.baselinemag.com/c/a/Projects-Processes/Eight-Fata...

Re:Rust is mostly safety by kbenson on Thursday December 29, 2016 @01:34PM (#13279041)
There was no error in the Toyota throttle control system. It was a pedal error with floor mats, and a separate pedal design error for other models.[1], combined with operator error. If you are interested, I highly recommend Malcolm Gladwell's podcast Revisionist History, which did an episode on this[2]. Long story short, your brakes can easily stop your engine at full open throttle, and in not much more space than braking without any throttle. Unfortunately, a foible of human behavior seems to lead us to get flustered and often not do the right thing in situations like these.

1: https://en.wikipedia.org/wiki/Sudden_unintended_acceleration...

2: http://revisionisthistory.com/episodes/08-blame-game

Re:Rust is mostly safety by 1wd on Thursday December 29, 2016 @03:22PM (#13279809)
I agree that the pedal design, human error and floor mat problems are much more likely causes. I don't claim it was a software error for sure. My understanding is that indeed no specific software error was identified, but it also was never ruled out for sure. Neither of the two links seem to contain anything to that effect either.
Re:Rust is mostly safety by kbenson on Thursday December 29, 2016 @03:52PM (#13280031)
To my memory, the podcast lays out a fairly comprehensive argument that it was just human error in the case of mechanical problems (as we'll as noting the car computers in all the cases show the brake wasn't pushed), and back it up with decades of research showing that this is a common problem, so that's about as close to definitive as you can get in this situation IMHO.
Re:Rust is mostly safety by smitherfield on Thursday December 29, 2016 @04:01PM (#13280096)
> Errors in the software of the radiation therapy machine Therac-25…

Caused by unsigned 8-bit integer overflow combined with (presumably) treating 0 as falsy. May or may not have been solved by using Rust (but probably wouldn't have because it sounds like a logic error in "clever" code).

> Errors in the software of a MIM-104 Patriot…

Caused by loss of precision in floating-point calculations. Would not have been solved by using Rust.

The other two were more likely human or mechanical than (unspecified) software errors.

Re:Rust is mostly safety by steveklabnik on Thursday December 29, 2016 @04:06PM (#13280131)
Integer overflow is defined to panic in debug builds, and either do that or two's compliment overflow in release builds. The current implementation overflows. However, zero is not false.
Re:Rust is mostly safety by smitherfield on Thursday December 29, 2016 @04:16PM (#13280200)
I assume that treating 0 as false was intentional in this case (it probably was written in PDP-11 ASM) and a direct translation of the Therac code therefore would be

  if counter > 0 {
      deploy_radiation_shield();
  }
Re:Rust is mostly safety by steveklabnik on Thursday December 29, 2016 @04:22PM (#13280234)
Yeah, you'd certainly have to see the actual code to be sure, I bet you're right.
Re:Rust is mostly safety by dwaltrip on Thursday December 29, 2016 @02:47PM (#13279538)
How many people have died from terrible UIs in apps that are commonly used while driving? Obviously, personal responsibility is primary here, but I don't think the app designers and builders should be absolved of all guilt.

I was just thinking about this the other day when using Spotify in the car. Spotify's UI is pretty good, but after they lost all my saved songs, I've had to resort to only using playlists, which require 3x as many clicks to add a song.

Re:Rust is mostly safety by hyperpape on Thursday December 29, 2016 @10:31AM (#13277778)
Three deaths from the Therac-25: https://en.wikipedia.org/wiki/Therac-25.
Re:Rust is mostly safety by geodel on Thursday December 29, 2016 @09:37AM (#13277447)
Yes as we move forward we should strive for more safety but 'countless lives lost' looks to blame software for that.

I think realistically we need to ask: would it be a better situation if no system program were allowed for lack of safety. Because I think humanity in general is better with existence of unsafe software vs no software exist at all unless it is safe as per rigorous safety standards.

Re:Rust is mostly safety by nickpsecurity on Thursday December 29, 2016 @11:25AM (#13278156)
It was a dumb statement unless he meant... given context of software maintenance... lives "wasted" toiling away on C or C++ monoliths. There are indeed countless lives and billions wasted on that that might be reduced or situation improved by better tooling.
Re:Rust is mostly safety by fungos on Thursday December 29, 2016 @10:38AM (#13277829)
Even by solving safety, erros in software will still happen. The software errors cited are much more about bad engineering, something that can't be solved by safety only.