Donald Stanfield
Well-Known Member
Maybe I'm just doing different shit with my computers but both my Mac and my steam deck need to be frequently rebooted. I do agree that Rivian can prioritize stability and responsiveness. I'll reiterate what I said about being an owner since '22, and seeing that the software package stability seems to move in cycles, where we will get a few updates that are slammed with features, but reduce stability and then new feature rollout will be paused to streamline things.Absolutely correct. So much so that Rivian is likely only afloat because of how much better their software is then VW’s and the CEO’s ability to sell access to that software to VW.
As incorrect as the first statement was correct. I’m not even talking about Linux machines sitting on a shelf quietly doing work for years (or decades) without an unscheduled reboot, and months between scheduled reboots. I have a steam deck that has never glitched out and needed a reboot, it has been rebooted for a software update. Once (to be honest I’ve only owned it a month). I have a Mac that hasn’t rebooted itself or been rebooted by me to “fix stuff” since I bought it around a year ago. It replaces another that had a similar history for three years (replaced because it is my primary work computer and faster is better and I work for myself so I asked my boss to make me more productive since I’m his only employee...).
Computer systems can be made stable, and they can be made with very few bugs. Both things require a commitment that the industry leaders tend to lack.
I expect if Rivian wanted to make “reboots” a thing of the past they could focus on that and have it done in six months or so, but at the expense of basically anything else. Which might be a good tradeoff, except that very likely also includes “work they committed to do on behalf of VW” and given the size of VW’s loan/investments based on software I suspect that would end Rivian just as surly as if they decided to cancel the R2 and the public announcement was “because it doesn’t match my pants”.
Likewise if Rivian decided that making the infotainment system buttery smooth and instantly responsive (say 1/20th of a second response tip to any tap) they could make that happen as well. It would require a pause on other efforts and a commitment. The “other efforts” suffering from lack of attention would include bringup of the R2 and R3 software stacks and VW work. So that is a non-starter. However I think this at least could actually be done in parallel, but it would take a lot longer.
Personally as important as “the infotainment system should never crash while I’m driving” is, and as important as “it should never take so long to respond to a tap that I wonder if the infotainment system HAS crashed” both are, making the actual part of the software stack that controls the motors rock solid, and bringing it up for R2/R3 and VW are all more important.
Hell, making “Alexa navigate to McDonald’s in Darby VT” not decide some address in PA is the ideal target is arguably more important then a buttery smooth UI (for people unfamiliar with new england geography, Darby VT is in north east Vermont, PA isn’t even in New England, although it touched New England, and I was in north central VT when I asked for the route and at the time I was on a route that took me somewhere in north west VT, so this was a miss by hundreds of miles that should have been a fairly easy hit...and it wasn’t even an explicable miss like finding a McD’s close to my current position)
This problem could likely be fixed by Rivian slowing down their software release cadence but then we would have people complaining about that. I think the point I'm trying to make is there is no perfect solution on anything and while my Macbook might be more stable than my Rivian the improvements come at a significantly slower pace, if at all.
Sponsored