I know enough about the software in BMW (NBT/OS7) and Audi (MIB2/MIB3) instrument cluster stacks to know there's at least as much complexity — if not substantially more — in many of the legacy brands. Not to mention the exponential complexity which comes from their highly modularised approach, where systems from a variety of external suppliers have to co-ordinate with each other.
By contrast, the Tesla software stack is (or appears to be based on a few minutes of research) shockingly straightforward considering its apparent complexity. Rather than being a hodge-podge of vendor software, it appears to be Qt-based software running within a Linux environment on Nvidia and/or Intel chipsets. Reviewers routinely praise the screen for being responsive and "iPad like". If there's a bloat issue, it'd be interesting to hear some specifics.
As for your quip about "decades of careful evolution in HMI and TCB design" you might have been right 20–30 years ago.
By contrast, the Tesla software stack is (or appears to be based on a few minutes of research) shockingly straightforward considering its apparent complexity. Rather than being a hodge-podge of vendor software, it appears to be Qt-based software running within a Linux environment on Nvidia and/or Intel chipsets. Reviewers routinely praise the screen for being responsive and "iPad like". If there's a bloat issue, it'd be interesting to hear some specifics.
As for your quip about "decades of careful evolution in HMI and TCB design" you might have been right 20–30 years ago.