3 ms·

The answer is patches. The more complex and "smart" something gets the more patches you need. And since you dont want to go to the mechanic every time, firmware

The answer is patches. The more complex and "smart" something gets the more patches you need. And since you dont want to go to the mechanic every time, firmware over the air it is.

nobody9999 5y ago
>The answer is patches. The more complex and "smart" something gets the more patches you need. And since you dont want to go to the mechanic every time, firmware over the air it is. Maybe in your vehicle. But certainly never in mine. Any vehicle whose software can be remotely modified is one I'll never buy. As I said, that's a disaster waiting to happen.
- signatoremo 5y ago
  A bug that affects your car that don’t get patched timely is also a disaster waiting to happen. Clearly it’s a risk model that you are willing to accept. I am not.
  - deleted 5y ago
    [deleted]
- cf141q5325 5y ago
  I absolutely agree, however that likely means no self driving car for either of us for the given reason. Unless you are planing on weekly trips to the mechanic?
  - nobody9999 5y ago
    >Unless you are planing on weekly trips to the mechanic? What? To install nightly builds? I think not. I wouldn't put software into production (or even beta) that required weekly updates. And that's just for software to make a website or other app go, with no risk of injury or death. Why would anyone want to be driven around in a vehicle by software that's so buggy it needs weekly updates? How often do you update the firmware in production systems? And a commercial self-driving car definitely needs to be production quality, no?
    - cf141q5325 5y ago
      I think you massively overestimate the code quality in automotive. Weekly might be a hyperbole, but from what i gathered from friends in the industry, the situation is as abysmal as everywhere else. I dont have any hopes that this will somehow get better with more complex software. Would love to be wrong here though

The answer is patches. The more complex and "smart" something gets the more patches you need. And since you dont want to go to the mechanic every time, firmware over the air it is.

nobody9999 5y ago

>The answer is patches. The more complex and "smart" something gets the more patches you need. And since you dont want to go to the mechanic every time, firmware over the air it is. Maybe in your vehicle. But certainly never in mine. Any vehicle whose software can be remotely modified is one I'll never buy. As I said, that's a disaster waiting to happen.

signatoremo 5y ago
A bug that affects your car that don’t get patched timely is also a disaster waiting to happen. Clearly it’s a risk model that you are willing to accept. I am not.
- deleted 5y ago
  [deleted]
cf141q5325 5y ago
I absolutely agree, however that likely means no self driving car for either of us for the given reason. Unless you are planing on weekly trips to the mechanic?
- nobody9999 5y ago
  >Unless you are planing on weekly trips to the mechanic? What? To install nightly builds? I think not. I wouldn't put software into production (or even beta) that required weekly updates. And that's just for software to make a website or other app go, with no risk of injury or death. Why would anyone want to be driven around in a vehicle by software that's so buggy it needs weekly updates? How often do you update the firmware in production systems? And a commercial self-driving car definitely needs to be production quality, no?
  - cf141q5325 5y ago
    I think you massively overestimate the code quality in automotive. Weekly might be a hyperbole, but from what i gathered from friends in the industry, the situation is as abysmal as everywhere else. I dont have any hopes that this will somehow get better with more complex software. Would love to be wrong here though