Live data from Hacker News

Automakers are starting to admit that drivers hate touchscreens

slate.com

371–380 of 1001 posts

Re: Automakers are starting to admit that drivers hate touchscreens

#371

I wouldn't mind touchscreens as long as these imbecile developers would strictly limit UI response time to under 16ms. In no world where you're barrelling 3,000+ lbs of mass at tens of miles an hour should you be distracted by some moronic app or subsystem failing to respond in time because it was written by under-experienced software "engineers." Any software running as a part of a motor vehicle should be federally…

> So what? You've got physical buttons? Big whoop. That physical button that takes 500ms to respond is still as dangerous.

No, that's wrong. Problem with touchscreens is that (1) you need to look at them and (2) there is no tactile feedback of whether you pressed it or not and (3) you need to hover your arm in a moving car at just the right spot.

Physical buttons cleanly resolve all of these major problems.

If the actual action has a perceptible delay, that's annoying but not dangerous. Given that with a physical button you didn't have to take your eyes off the road and given the tactile feedback you know for sure you activated/pressed/moved the control, you know the control has been activated even if the effect is delayed.

With a touch screen, if there is a delay, you'll have to keep taking your eyes off the road again and again, triple checking if you pressed on the right spot or not.

Re: Automakers are starting to admit that drivers hate touchscreens

#373

I wouldn't mind touchscreens as long as these imbecile developers would strictly limit UI response time to under 16ms. In no world where you're barrelling 3,000+ lbs of mass at tens of miles an hour should you be distracted by some moronic app or subsystem failing to respond in time because it was written by under-experienced software "engineers." Any software running as a part of a motor vehicle should be federally…

[deleted]

Re: Automakers are starting to admit that drivers hate touchscreens

#374

I wouldn't mind touchscreens as long as these imbecile developers would strictly limit UI response time to under 16ms. In no world where you're barrelling 3,000+ lbs of mass at tens of miles an hour should you be distracted by some moronic app or subsystem failing to respond in time because it was written by under-experienced software "engineers." Any software running as a part of a motor vehicle should be federally…

> because it was written by under-experienced software "engineers." I used to be an infotainment software engineer for an Auto maker. There’s this idea in the software industry that because the software behaves poorly on your car’s system, it must’ve been written poorly by someone who didn’t know what they were doing. In my experience it was almost always a matter of the hardware being stretched way past its limits.…

Windows 95 runs pretty well on 10 year old hw and does much more than these car screens do. So no, software is fundamentally crap there.

Re: Automakers are starting to admit that drivers hate touchscreens

#375

Earlier quoted context omitted.

I believe that the engineers are competent at developing software, and think that a lot of the quality issues are due to engineers abdicating authority over the software to managers and never saying "No, adding in that feature at this point in the timeline is going to make this a steaming pile of shit and I refuse to do it and still call myself a software engineer." I get that we have families to feed, but I've seen…

The industry works as follows: the OEM (Daimler, Toyota etc.) says they want a software spec implemented. Other companies (Tier 1 suppliers) bid to win the contract. The cheapest usually wins. If you have a company and refuse to take the crazy deadlines and low quality and low pay then don't worry, there is another Tier 1 supplier across the street who will do it for you. OEMs know that you need them more than they n…

That’s fine. But the worst case response time across the entire UI must be the first item on that spec! That spec is of course the responsibility of the OEM to create. Where this goes wrong I don’t know but competition, price sensitivity etc doesn’t explain it. Having soft and hard limits for response time seems obvious and someone either forgot, or they had a meeting where they (the OEM, after deciding on a solution and having it implemented) said “ok we can save $20 on the BOM by going for a cheaper SoC if we accept 200ms response times instead of 50ms” and that should basically be criminal due to the safety aspect.

Re: Automakers are starting to admit that drivers hate touchscreens

#376

I wouldn't mind touchscreens as long as these imbecile developers would strictly limit UI response time to under 16ms. In no world where you're barrelling 3,000+ lbs of mass at tens of miles an hour should you be distracted by some moronic app or subsystem failing to respond in time because it was written by under-experienced software "engineers." Any software running as a part of a motor vehicle should be federally…

> because it was written by under-experienced software "engineers." I used to be an infotainment software engineer for an Auto maker. There’s this idea in the software industry that because the software behaves poorly on your car’s system, it must’ve been written poorly by someone who didn’t know what they were doing. In my experience it was almost always a matter of the hardware being stretched way past its limits.…

I wouldn’t necessarily the engineers, but I’ll certainly blame the designers and product managers.

I absolutely hate my Acura’s infotainment system. My “favorite” feature isGPS autocomplete.

You type in part of an address (which of course has a very slow response time), then you pick the completion off the list.

Sounds fine right?

But when you click it, you’re met with a SLOW ANIMATION OF THE COMPLETION BEING TYPED INTO THE SEARCH BOX. Motherfuck dude! What the hell is that? Why does anyone want to watch the keyboard flash for five seconds?

Re: Automakers are starting to admit that drivers hate touchscreens

#377

Earlier quoted context omitted.

I believe that the engineers are competent at developing software, and think that a lot of the quality issues are due to engineers abdicating authority over the software to managers and never saying "No, adding in that feature at this point in the timeline is going to make this a steaming pile of shit and I refuse to do it and still call myself a software engineer." I get that we have families to feed, but I've seen…

There's no incentive for an engineer to do that. Saying yes and delivering crap gets you a bonus, hard truths get you shuffled around or made redundant. There's no real consequence for delivering crap, so that's what happens. Contrast this with other engineering fields, where the engineer is truly responsible for the decisions they make. My civil engineer friends face losing their licenses, fines or jail time if they…

"My civil engineer friends face losing their licenses, fines or jail time if they are found professionally negligent."

These standards ought to be applied more widely and done in conjunction with tightened consumer law. In many cases the quality of electronics equipment has gone to the dogs. I could give instances of appliances I use that can only be used in a hobbled mode—numbers of published functions simply don't work—because their firmware bugs are so bad.

These devices are so bad they wouldn't pass as early developmental mockups let alone early prototypes in a professional engineering establishment. I'm damned if I know why the hell consumers put up with the situation and haven't revolted, it remains a mystery.

Things won't improve until they do.

Re: Automakers are starting to admit that drivers hate touchscreens

#379

Earlier quoted context omitted.

> because it was written by under-experienced software "engineers." I used to be an infotainment software engineer for an Auto maker. There’s this idea in the software industry that because the software behaves poorly on your car’s system, it must’ve been written poorly by someone who didn’t know what they were doing. In my experience it was almost always a matter of the hardware being stretched way past its limits.…

I believe that the engineers are competent at developing software, and think that a lot of the quality issues are due to engineers abdicating authority over the software to managers and never saying "No, adding in that feature at this point in the timeline is going to make this a steaming pile of shit and I refuse to do it and still call myself a software engineer." I get that we have families to feed, but I've seen…

Those managers might be right from a sales point of view. Until we buy all this, they are right.

Let’s see that Tesla can change this or not.

Post reply on HN