Live data from Hacker News

Software is eating the car

spectrum.ieee.org

331–340 of 549 posts

Re: Software is eating the car

#331

Earlier quoted context omitted.

Car guy here. Yeah, I’m with you. My favorite car was a ‘96 Tercel with mechanical steering and a 4-speed manual. It even had manual roll-up windows. It had less than 100 HP, but it was simple as hell to operate, very fun to drive, cheap to maintain, and extremely reliable up until I sold it with nearly 400k miles on the odo. I put an aftermarket stereo and speakers in it and I was set. Only reason I sold it was beca…

Those mid 90s Japanese sedans were awesome. Relatively compact overall, zippy little 4 cylinders engines and manual transmissions. I had an Accord from that era, and loved driving my dads nerdy-as-hell Nissan Sentra. That car was shockingly fun to drive.

Just sold my 1990 Bluebird. Didn't pass warrant of fitness, but otherwise drove amazingly well.

Re: Software is eating the car

#332
post #7

Earlier quoted context omitted.

Glad to hear I'm not the only one who wants a dumb car. Unfortunately, the idea of electric cars has become bound up with the notion of software-driven cars. I want an electric car with analog controls, no touch screens or over-the-air updates, and minimal software. A car that I feel like I own, rather than one I'm getting a click-through license to use.

Mazda has been actively removing touch screens in new models. The screens are still there, but the touch part is replaced with physical controls for cabin features/radio and a puck controller for other stuff.

I know HN loves to hate on touchscreens in cars but I don't really get it. Both cars I own and almost every car I've rented in the last few years (that's quite a few) has had a touchscreen. This is pretty much always how it works: 1) The most used functions have physical buttons and knobs, often on both the steering wheel and the center console 2) Touchscreen is used for uncommonly done things, like adding new Bluetooth connections and adjusting radio settings 3) If the vehicle is moving there are limits on touchscreen use (like the touchscreen will refuse to work after X clicks, or disallow some functions, or both.)

This seems ... fine.

Re: Software is eating the car

#333

Earlier quoted context omitted.

Modern cars have more design features that improve crash survivability (better airbags, better crumple zones, tested with more realistic crash tests, etc). Those seem like a pretty unalloyed improvement to me. I'm not saying you're wrong about the things you mentioned, but cars really have got safer, in important ways.

yes, airbags and crumple zones do improve safety, but even those are not without negative consequences, like bigger, heavier vehicles (which is more dangerous to others) and higher sense of psychological safety leading to being less considerate, less attentive, and more reckless. that's not to argue that those tradeoffs aren't net positive, but that they're still tradeoffs to be considered, rather than short-circuiti…

I'd argue feeling safe when I drive is net positive for actual safety. Stressed drivers going to make way more errors.

Re: Software is eating the car

#334

Earlier quoted context omitted.

Good point, you are totally right. I don't drive a car which uses the infotainment system for mission-critical functionality. I've actually run it without the infotainment system in the car at all. Tesla's would effectively be bricked without the head unit functioning. Ford and the rest of the reputable OEMs know a thing or two about flash degradation though. It was actually a huge sticking point in one of my infotai…

If you are allowed to share, what is the typical OEM specified lifetime for the infotainment flash part? I guessed 10 years in my original comment, but that was a gut instinct and completely uninformed.

Your guess would be nearly as good as mine, I worked as a vendor and never actually had to abide by the requirements the integrators over at the OEMs had to stick to.

Usually when talking with them they would throw around "lifetime of the vehicle" requirements. For typical OEMs I think they consider that 15-20 years. Tesla, probably 10 lol!

Though, in reality, if you baby your flash to last 15-20 years. You've probably designed it in a way that it has a chance to live a whole lot longer.

Re: Software is eating the car

#335
post #234

Earlier 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?

Musk coming from software they seem to actually adopted modern software engineering practices that other manufacturers going to struggle with for some time. Being vertically integrated helps heaps too.

Re: Software is eating the car

#336

I'm amazed that in this entire article Autosar wasn't mentioned once. The giant 2 ton elephant in the room here is automotives reliance on god-awful "kitchen sink" style standards. Try reading through the various Autosar docs and ask yourself if you expect robust bug-free code to be written to comply with it. There needs to be a complete cleaning-of-house in automotive software. I2C, Flexray, Ethernet, CAN/CANFD & OB…

I worked in the automotive industry and I can totally confirm. The worse thing is, there are now AUTOSAR experts and AUTOSAR tools and AUTOSAR Tool Experts and within that tool there’s a ARXML generator that’s generated with another tool …

There’s no way this can ever become safe, robust, software. The worse part is, there’s so many careers that depend on this obscure skillset that I am unsure a change can come from existing companies.

Re: Software is eating the car

#337
post #283

Nothing worse than automotive software. Buggy, slow, terrible user interfaces, outright dangerous and in many ways much worse than the systems they replace or augment. The automotive industry has a long long way to come - assuming it will happen at all - before they can be said to be responsible software vendors. Case in point: my - former - C class Mercedes that made two pretty good attempts to kill me by slamming o…

One of the main problems is that we have many different software teams trying to solve the same safety feature driven functions in many different ways with many different solutions, outcomes, and decisions along the way. This leads to a very fragmented base of software with varying levels of safety, none of which is tested to the same standards. The result is that consumers don't know of the car they are buying is tr…

This is something agencies like NHTSA and/or private companies like IIHS are supposed to solve, but most active safety technology testing is just ‘does it work’ in very easy scenarios - the test suite needs to include many environments and tough conditions if it wants to evaluate these systems more broadly (The only issue being when car companies optimize for those specific tests, or ‘when the measure becomes a target’).

Re: Software is eating the car

#338

Earlier quoted context omitted.

It's not that it's visually distracting that's the problem - it's that you can't feel where the buttons are without looking. And if you aren't looking you'll accidentally do things you didn't mean to, like press escape, or turn your mac off when trying to hit back space.

To be fair, I don't use my function keys on my laptop enough to where it became muscle memory, especially for the alternative functions they provide (screen brightness, media, etc).

Apple had those keys in the same place for ages, and they're all set to the the action rather than function by default. Volume up and down is useful, as is escape and the power button. Key brightness is handy, play/pause I used to use a lot. So looking forward to finally getting a new laptop when the M1 Macbook Pro comes out.

Re: Software is eating the car

#339
post #194
post #7

Earlier quoted context omitted.

Glad to hear I'm not the only one who wants a dumb car. Unfortunately, the idea of electric cars has become bound up with the notion of software-driven cars. I want an electric car with analog controls, no touch screens or over-the-air updates, and minimal software. A car that I feel like I own, rather than one I'm getting a click-through license to use.

So you want a mechanical door lock, manual windows, no car stereo, no power steering, no thermostat, no cruise control, etc... The problem with that dumb car is that it is missing that very convenient feature. So you want a dumb car but with feature X, because feature X is really great. But the other guy will not care about X and will think it is bloat, but Y is really important, while for someone else, it will be al…

The features you mention aren't any more "smart" than an intermittent wiper is, which was invented long before electronics appeared in cars, much less digital logic.

US luxury cars in 1965 had all the features you mention. They were delightfully dumb and simple to operate. That's what I want now: knobs, sliders, and buttons that move and click when my finger pushes them.

Re: Software is eating the car

#340

Earlier quoted context omitted.

oh its funny.. of all the rust trend storm I cannot recall one mention of automotive industry usage (not that I imply it's not used.. I just don't remember hearing about that).. this is a place where I'd really love safer languages. btw any embedded car ADA shops ?

There are some rumblings of Rust in automotive, but nothing I can publicly point you to definitively.

come on, let's put more rust onto the metal
Post reply on HN