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.…
Dude Winamp was a clean, simple and wickedly responsive UI that allowed a multitude of real-time audio tweaks and supported playlists with thousands of files. This was in the late 90’s running on 166Mhz processors with maybe 16MB of system ram. Are you saying modern car infotainment systems have fewer resources allocated to the UI?
Relatively speaking: Yes.
Response lag is always because the hardware is chugging to process all the bits in time (they're not in time). Between underprovisioned hardware and shittily written software, hell yeah fewer resources are allocated to the UI.
We need a small supercomputer's worth of resources allocated to bring the software of today up to snap like it was the 90s.