[bsagdiyev]

It absolutely is not. I do not want my 2 ton moving vehicle updated on a whim. My 2019 has a screen I can never really turn off that is bright at night, my 2008 has a slow laggy UI that an update will never fix. The 2000 Miata sitting in my garage has the best interface of them all. Push buttons and dials for climate control, two window switches in the middle tombstone area and that's really it outside the typical steering wheel controls for signals, lights and windshield wipers. It's amazingly simple and should continue working even when my newer cars are dead and gone.

[bsagdiyev]

Since I cannot directly reply to you (ajconway) -- this is thoroughly untrue. Tesla does it at the very least and I'm aware that is becoming a "feature" offered in other vehicles now too.

[macintux]

If you click/tap on the time stamp next to a message you reach a dedicated page where you can reply (same thing I had to do to reply to yours at this conversation depth).

[bsagdiyev]

Well what do you know, TIL. Thank you!

[datavirtue]

I always marveled at the competence and refinement of automotive interfaces...they killed that shit.

[ajconway]

> I do not want my 2 ton moving vehicle updated on a whim.

The car won't update itself, so:

1. Ignore any updates as they become available.

2. Problem solved.

[MereInterest]

For devices that connect to the internet, such as for updating maps and real-time traffic data, does the lack of security updates mean that your 2-ton moving vehicle is now somebody else's 2-ton moving vehicle?

[pjmorris]

Which is actually an argument for non-updatability.

[MereInterest]

Completely agreed. Mainly, I wanted to make a distinction between "cannot be updated" and "can be updated but isn't". The former is a design choice that removes entire classes of vulnerabilities. The latter is a usage choice that keeps vulnerabilities open.