News for hackers. Stuff that matters.
Re:A Tragic Loss by npizzolato on Thursday June 30, 2016 @05:29PM (#12011910)
I half expected the final paragraph offering condolences to end with "but remember, this really wasn't Tesla's fault!" The third paragraph reads like Tesla is trying to wash their hands as much as possible. "Remember, he clicked all these buttons. He knew what he was getting into!"
Re:A Tragic Loss by jsprogrammer on Thursday June 30, 2016 @07:11PM (#12012594)
It really makes you consider why you would even want such an autopilot. From the description in this eulogy, it sounds like you must work even harder with autopilot on than if you were driving manually. Not only do you need to have the same alertness as manual driving, you also have to be ready to take over at any moment and try to detect if the autopilot has made any mistakes that might guillotine you, or worse.
Re:A Tragic Loss by Animats on Thursday June 30, 2016 @06:11PM (#12012234)
Yes. Last time, their excuse was "but the driver should have known that in firmware revision 6.2 and later, tapping the brake disables automatic braking".

This time, there's an interesting question. Did Tesla remotely access the crash data after the crash? Did they alter any data? Is that verifiable? The NTSB will probably explore that issue. The crash data record in an airbag controller becomes read-only when the airbag fires.

Re:A Tragic Loss by alxndr on Tuesday July 05, 2016 @11:53PM (#12041103)
Gives a new meaning to semver's term "breaking changes".