ATLRivvy
Well-Known Member
What? Tradeoffs doesn’t mean fully sacrifice one thing for another - cadence / complexity doesn’t matter when the tradeoff is failures on basic functionality. That’s the point both the OP and I are making. No one cares how many holiday updates or rarely used drive modes you add if the tradeoff is inconsistent PAAK functionality, random sensor errors when driving, etc. Customers don’t forgive you for getting the basics wrong in the name of chasing monthly trinkets.Apparently you don't know about the tradeoffs because you're whining while admitting no one else touches the cadence and complexity of Rivian's software updates. I don't care what you do for a living, but it doesn't seem like you understand what you were buying with your Rivian, when there are hundreds of threads you could have read before making your purchase. If you had, you wouldn't be in your current situation and the rest of us who had the correct expectations wouldn't be bothered with you making mountains out of mole hills.
I very well understood what I was buying - a developing software platform that would hopefully get better over time. It has gotten better - just not at great enough speed. That doesn’t mean forgive basic problems.
Accessing the car is one of the most frequent things people do, same for listening to music in their car, using the ADAS, navigating to a destination, messaging, etc. when it comes to shopping for cars these days those are the mountains. Being reliable at those things aren’t extras, it’s tablestakes for mass market high-end EV success these days. If that isn’t part of your expectations then so be it, but there is nothing “correct” about expecting inconsistency on tablestakes functionality.
Sponsored