I can't really help with what you're specifically looking for, but I'm pretty sure my grandfather worked on these as an engineer. He retired from Boeing in 1985. Died almost 20 years ago.
Indeed, this can be way further optimized.
For example, you can probably do a wasm-strip and wasm-opt passes that would leave the wasm file being ~5-10Mb. Still very big, but a bit more reasonable.
The good thing is that thanks to Nuitka you could actually do some tree shaking and only include the imported files and not everything in between (although this might break other behavior such as eval and so).
Hertz also had absurd policies like bring the EV back 100% charged. Which is basically impossible unless there is a DC fast charger adjacent to the rental car center.
Yes. This was the policy I saw when I considered renting an EV in Phoenix. We were only going to be there for 27 hours and our hotel did not have its Level 2 charger operational yet, so we opted for a gas car instead.
I rented a Bolt from Hertz last December and their policy at the time was:
“Return your EV at the same charge level as pick-up and pay $0. Or return your EV at any level for a $25 Recharge Fee.”
They were pretty lenient about the return charge — it was close to 100% to start and 80% when I returned it, but they didn’t charge me the $25. Even if they had, the EV rental rate was cheap enough that I would’ve still come out ahead vs. renting a gas car.
I'd been hoping projects like wasmtime could end up looking like a Docker alternative for server side things. Do you think that's unlikely to pan out without a lot more work that doesn't seem to be happening?
A lot of those are powered by wasmtime or WasmEdge.
If you’re wanting to be able to just pull down a random app and run it as wasm, that’s inherently harder with wasm, because you have to recompile, and amazing compiling stuff is always harder than it should be. For example I compiled jq to wasm to other day, so you dont have to worry (as much) about the CVEs that was issued recently. https://github.com/rockwotj/jq-wasi
Repeating what you said in my own words to ensure I understand it.
I think you're suggesting they might have a canary fleet, but there wasn't anything/enough that preventing a mistake from bypassing the carry fleet before going to production?
I hadn't heard about the Volvo one! I had a 2022 Volvo C40 before I got my Rivian R1T.
When I first got the Volvo the GPS and LTE connection would periodically stop working for a day or two. They pushed a fix for it. Later they added CarPlay, which wasn't there when I got the car. Good updates. But not as frequent at Rivian.
Was Volvo able to fix it with another OTA or did people have to go in for service?
Beats being so poor you can't afford a car, or the only car you can afford is slowly rusting itself away or one no-longer-mass-produced part away from making a repair out of your financial reach. I'd take bad OTA updates anyday.
Seems like this batch of half baked cars receiving OTA updates are more likely to be the ones that are in repairable in the not so distant future, whereas parts for a 1990s toyota gmc or ford anything can be found cheaply and installed by any ambitious teenager.
GP is referencing the "having the being stolen from stolen".
Nevermind that the wealthy ain't fretting for one second over OTA updates. Imagine a personal vehicle budget where the Porsche is technically your daily driver, but you never drive it because you're driven everywhere.
In the case of Rivian they have been pushing very meaningful improvements on a roughly monthly basis via OTA.
I got my R1T in June 2023 and since here are a few things they've improved, just off the top of my head, not bothering to look it up:
1. Significant improvement to ride quality via different / better suspension tuning.
2. Ability to schedule warming the cabin and pre-condition the battery
3. Completely redesigned the UX for setting drive modes and suspension height (for the better IMO)
4. Added a ton of car info, like battery temp, motor temp, and other info like altitude, various angles the vehicle is at (for off-roading), degrees the front wheels are turned
5. Added additional settings for ride softness / firmness (I got this update yesterday and haven't tried it yet)
When an update is ready I get a notification in the car and from the Rivian app on my phone. I can just hit apply and it installs it.
IMO a USB install would be a substantially worse experience and it would be much less likely that customers would actually install it.
But, for the type of person who just wants the car to stay the same as it was the day they bought it, and never change, it's not the vehicle for them. Personally I really like that it's continually improving and I don't have to go in for service or even go out to the truck to do an update.
It's not that I don't want improvements, I modify my cars for exactly that reason, but I want reliability. Improvement to the ride quality shouldn't be a manufacturers after-thought. UX adjustments are nice, adding further visibility to system features, great. OTA updates on systems impacting car functionality or safety, no. These things should be tested thoroughly enough before release to not require periodic updating. They should be stable and tested enough that an difficult to apply update is a reasonable cost. These are not the systems to fail and fix on repeat.
> But, for the type of person who just wants the car to stay the same as it was the day they bought it, and never change, it's not the vehicle for them.
I never said I didn't want updates. What I said is that I want to understand what the updates are and then choose to upgrade or downgrade when and how I see fit. Or better yet make the updates OSS and then let me do my own builds with the features and functionality I prefer as they are developed.
One thing that is right is that a Rivian is not for me, for a lot of additional reasons.
I wasn't trying to suggest what you personally want or don't want. Just that I could see how some people do not want their car interface to change, or even ride quality to change.
https://github.com/vitessio/vitess/graphs/contributors?from=...