5 ms·
I can’t be the only one disappointed in this. Making cars at scale up to modern standards is really hard. Making great software is also really hard. I have seri
by naravara 7y ago
I can’t be the only one disappointed in this. Making cars at scale up to modern standards is really hard. Making great software is also really hard. I have serious doubts as to whether a company that does the former can have the culture, management practices, etc. to execute really well on the latter.
The fact that Apple shut down its car division suggests there may have been some issues going the other way.
I wish they’d have moved towards standardizing APIs and “controllers” throughout the automotive world and just encouraged after-market infotainment systems to fill the functionality gap. I just really don’t like that Infotainment ends up having to be a complicating factor in buying a car. It’s hard enough to pick one out that ticks all the functional boxes and feels nice to drive. But then suddenly you get cars that feel great, but neglected the interface design or had a slow UI and suddenly they’ve ruined it.
- kortex 7y agoI think a standard API would be great. "Here's the things the ecu should be willing to expose": basically all the usual EC2 reader registers, as read only. Here's a standard climate control API, which doesn't touch the ecu stack. And here's some mixins/ flexible RPCs so vendors can add custom functionality. Alas, this limits vendor lock in, so that's precisely why I think it's unlikely to happen.