Ok, if we're going to snip each others' text to nothingness and then soapbox about it, so be it. I see you confirm that you have no relevant engineering experience. I have some. In my experience engineers working on life-safety systems do not take the cavalier and reductive "well, we could all die anyway, so no point trying to mitigate new risk" view you seem to. I would assume this extends to Tesla's engineering staff of whom I do still hold a very high opinion.Correct. Just like you, I am a customer of Tesla. So unless you are also an engineer at Tesla....
So I was quite surprised to see them get this one so very wrong. Like many others I'd assumed the MCU couldn't cause this kind of failure (because well understood practices would reduce that possibility to a negligible level). I would expect someone at Tesla thought so too and screwed up. I hope they take it seriously enough to prioritize a fix but this is a problem that, to me, is different in kind than the other MCU bugs so many of us have seen. An issue that, given the experience I do have working on other embedded systems including user interfaces to dangerous machinery, I find very surprising and worrisome.
That's how it looks to me from the imperfect, non-comprehensive, but relevant experience I do have implementing life-safety systems. You admit you have none at all. What can I say?