3 ms·
Forget updates entirely. My car is one of the few places I expect to get software that works the first time. If you absolutely must have updates, then at least
by VyseofArcadia 3y ago
Forget updates entirely. My car is one of the few places I expect to get software that works the first time.
If you absolutely must have updates, then at least not OTA updates. Have them done at the dealership or service center so any issues can be dealt with immediately.
Come on, is this engineering or hacking? This is a car, not a CRUD app. Get. It. Right.
- w0m 3y agorandom new features via OTA updates was one of the deciding factors when i bought my car ... :) I also mostly WFH so... yea. lol.
- dalyons 3y agoeh i guess i disagree. We had that (& still do for some cars) for decades, and it universally resulted in terrible software that you were stuck with for the life of the car. Hard to update == hard to iterate == bad software.
- ClumsyPilot 3y agobad software is the one that kills people. Ugly software that works is fine
- dalyons 3y agoin cars it is often is ugly AND doesnt work.
- dagmx 3y agoThat’s how things used to be and it resulted in lots of long standing bugs because the update rates were low, and so manufacturers didn’t push updates. Many people don’t live near dealers or service centers or can afford the continued cost (it’s not free usually unless it’s a recall) OTA is better for consumer when done properly. Other manufacturers manage it fine, and one bad example shouldn’t be what we base things on. It’s what we should learn from and improve on.
- jacquesm 3y agoBut average quality was a bit higher because nobody thought 'oh, we'll fix that next week in the OTA update'.
- dagmx 3y agoI don’t think so. This is the same thought people apply to cartridge based games for example, before software updates. But the reality is that the same types of bugs would likely exist. Nothing about the engineering aspects has really changed other than more features. All that would happen is future revisions would have it fixed and early buyers would be stuck.
- jacquesm 3y agoThe types of bugs were similar but the bug count was entirely different. Typically on a 16K ROM you'd have two or three known bugs after the product was in the market for a while and maybe years later you'd find another one by re-reading the code and realizing that if you tweak things just so you can get the product to misbehave. But you're not looking at near endless lists of known issues and 'wontfix' wasn't a thing back then.