Short answer to the lede: no, the industry cannot cope. Or rather, it will limp along with bloatware, bugs, and malware exactly the same way we see desktop OSes bloat, or the way we see routers and set-top boxes hacked to become botnets. In my 40+ years in the industry I've yet to see code get SMALLER. With the exception of Linux kernel 1.0 in the 90's which was a step backwards into smaller, more compact code, code…
Software is eating the car
251–260 of 549 posts
Re: Software is eating the car
#252Earlier quoted context omitted.
I recently bought a used 2016 Spark EV (having a baby and needed something other than my motorbike). It does have a touchscreen, but mostly for extraneous information and radio functions. Everything else has dedicated knobs and buttons. (The one dumb thing is that the fan speed updates on the screen, rather than just having ticks above the knob.) It is a California "compliance car", which means it was just a modified…
I'm guessing that all-touch is just cheaper these days, no QA testing for all the little mechanical bits
Re: Software is eating the car
#253Re: Software is eating the car
#254In some ways that's a good thing: EVs require much less physical maintenance. (At least, their drivetrains need less maintenance. Whether the rest of the car does depends on the manufacturer.) But on the other hand, depending on how heavily locked-down the car is, it'll be hard to do third-party modifications and older vehicles are going to be at high risk of having security vulnerabilities as soon as software maintenance for old vehicles stops being a priority for the manufacturer.
Re: Software is eating the car
#255Earlier quoted context omitted.
Audi's 2022 e-tron GT moved back to more physical buttons, and only has one infotainment touch-screen, unlike a bunch of their 2021 models where there's at least two different infotainment screens.
I really miss "real buttons", meaning not just something tactile. Things like a power button that actually opens a circuit. Or a volume dial that doesn't lag because it's actually a potentiometer and not a rotary encoder. Too late for all that, I suppose.
Re: Software is eating the car
#256The problem with this is that auto companies are not software companies. They may have good engineers there, but they are hamstrung with a culture that considers software as an add on cost center at best. Perfect example: I have no way to report software bugs to Honda. I've found a few and collected detailed reproduction data. The best I can do is give it to a sales rep in the service department and hope they send it…
Games used to be shipped on chips to customers with the assumption that they could never be updated, but now the expectation that that's possible results in multi GB release day patches. Games used to be shipped to consoles without network access but if Blizzard goes out of business tomorrow, Starcraft II will just fail to boot because the software you get isn't enough to run the game. Games used to make most of their money by selling you a fun game that you wanted to play, but now they make most of their money from DLC's or selling in-game currency.
I don't want my car to move fast and break things. I don't want my car to fail to drive me to the hospital because it has updates to install. I don't want my car to drop features it had when I paid for it because some PM's bonus depends on me using their monetised features instead. I don't want my car to be measured by "works on my machine"-level QA. I don't want my car reporting telemetry. I don't want my car's UI to become unuseable over time because the developers shipping constant updates to it are working on the newer hardware instead of the hardware I have. I don't want parts of my car to stop working because an app developer doesn't support my car anymore. (I've lost access to many an iOS game because of this without changing any hardware myself.) I don't want my car to stop working because it doesn't support TLS 4.0 or 6g and the licence server requires it. I don't want my car to stop working because it can't find the licence server because Volvo went out of business, or even just decided they didn't want to support me anymore. I don't want my car to fail to unlock because of a network blip. I don't want my car to suggest I go to McDonald's instead because of an advertising deal.
That's what embracing the software industry's norms will get you. Awful QA, shortsighted dependencies, terrible incentives, and the ability to monetise you.
Re: Software is eating the car
#257Earlier quoted context omitted.
I really miss "real buttons", meaning not just something tactile. Things like a power button that actually opens a circuit. Or a volume dial that doesn't lag because it's actually a potentiometer and not a rotary encoder. Too late for all that, I suppose.
Though there's nothing preventing electronically controlled buttons working with imperceptible delay except crap software.
Re: Software is eating the car
#258Earlier quoted context omitted.
> If electric cars ever become widespread Exclude Tesla and most all EVs on the road today are just normal cars that happen to be electric.
Why is special about Tesla that makes them not a “normal” car that happens to be electric?
Re: Software is eating the car
#259Earlier quoted context omitted.
Lawyers tend to love it when their opponents think they've found a cute legal hack.
IANAL, but I'm curious if you are. In my experience, lawyers tend to get a lot done by intimidation. Remember all those ridiculous lawsuits from the RIAA over downloading illegal music? Well, it turns out when people actually took them to court they won every time. But people settled out of fear. Sure, if the lawyers are actually trying to do things legally first and adhering to the letter of the law, I'm sure they'r…
I think we're talking about two different things. Yes, the RIAA was running an intimidation campaign. By and large they didn't care about any particular case.
That's quite different than a plaintiff coming at a car manufacturer over sketchy click-wrap agreements.
Re: Software is eating the car
#260Earlier quoted context omitted.
Don't they still record and just upload when you go to the dealer and they plug in the cable?
There is an extremely limited amount of diagnostic data recorded by most cars (Tesla aside) - absolute limits, performance counters, and freeze-frame diagnostic data. There simply isn't much storage, and again, Tesla aside, most manufacturers don't want to have to buy high-write capable flash of the sort that could cope with constant logging. The most invasive is probably airbag blackbox data, which is stored upon de…