I’m also not a proper “watch guy”. I have one watch I wear daily and two vintage watches that don’t run very well and I don’t have the $$ to repair so they sit in a drawer.
Soviet watches are a great rabbit hole. Thankfully, I’ve managed to stay on the sidelines for the most part. I do have a CCCP automatic that will only keep time for more than one day if I wind it, but that’s it. There are a whole bunch of interesting designs out there though.
I bought a mechanical watch about five months ago and honestly, it’s been great. I’ve been through… way too many smart watches over nearly ten years and was getting tired of not getting more than two-three years out of them before something failed. It seemed wasteful. Yeah, standalone GPS tracking and what not was neat, but I nearly always have my phone on me these days. I wore watches, granted Iron Man and not mechanical, all through middle and highschool and ditched them when cellphones really started becoming ubiquitous. It’s funny how I’ve come full circle.
Most OEMs usually show an update screen on their radio, even if something unrelated is being updated.
If the update is taking a long time it could be a really big file on a SOC. It could also be a smaller file being written to… very slow internal memory because when the part was sourced 8 years ago no one considered including memory read/write speed in the sourcing documentation. I’m betting the second, unless this OEM didn’t include background programming on SOCs, which is kind of foolish given how much easier it is on a SOC than MCU.
I can’t speak for this particular OEM, but 12 volt lead acid batteries don’t have very deep power reserves. The OEM choosing to leave the battery on during programming is likely a method of ensuring there’s enough juice to install the update and start the car on the next attempt.
It’s a mix of piece coat optimization and a lot of creep in what used to be a pretty lightweight process throwing it into the ditch.
The things that run software in cars largely fall into one of two camps: MCUs and SOCs. Think Arduinos and Raspberry PIs. Background programming, with an active and inactive partition, is absolutely possible on a SOC. They’re even file based, so you can do all kinds of clever things. Cars tend to not have many SOCs, so it’s not a monumental task to pitch having them each coat a little bit more for extra storage/processing. The biggest hurdles here are automotive grade and the very long development cycles. These both mean that the hardware is 3+ years old when it launches.
MCUs tend to have monolithic software builds (think literally everything gets compiled into a single .exe). There are a million billion of these things in a typical vehicle from most automotive OEMs. It’s… very hard to make them all have more capacity because you would take that cost and multiply it by 40 or so to get all the MCUs on a vehicle ‘upgraded’ for extra capacity.
If this all sounds a little crazy, it is. From two angles. First: do we really need as much software control in cars as we do? Marketing departments seem to think so. Second: the reason why there are so many small compute units in a car is the slow migration from mechanically controlled components to electrically controlled on. Back in the 80s the majory of automatic transmissions shifted based on a very complex mechanical system (look up a transmission valve body if you’re curious). Moving that to electronic control meant adding a computer to control that functional. Now take this and multiply it and you’ll kind of see the wreck in motion. Most OEMs are moving toward more centralized compute (fewer, larger, and smarter control units), but new electrical architectures take a lot of time/effort so it’s slow going.
This is the big thing in my mind. It’s not that lemmy.world has the most users, it also has most of the active communities (at least in my case for my interests). When it’s down, interacting with those communities on other instances is… very weird.
I am aware of them, but given my general lack of focused fitness I am fairly ambivalent about a fitness tracker. I do spend a decent amount of time chasing my kida outside and take the stairs/park far away at work, but my smartphone does a good enough job at tracking those activities.
A smart watch/fitness tracker makes sense if you’re actively engaging in use cases that they will enhance, but that’s not the case for me right now. I just want an easy way of knowing what time it is and I’ve learned to manage notifications on my phone so the important ones still catch my attention.