You're used to consumer software updates that have been tested over literally billions of updates. And they're brilliant - they mostly just work well enough that you don't expect your phone or computer to get bricked during one. But there are rare cases where something goes wrong and they do get bricked. For something like the first ever software update in space, I'd expect the chances of something catastrophic happening would be much higher.
I'm used to writing bootloaders and firmware update systems for heavy equipment with impatient users who do terrible, terrible things to their hardware. Remote software updates fail all the time, for all sorts of reasons, but the things you need to do to come back up 'no worse than when you started' has been known for years.
If you make any sort of device and your updates can brick the device, you suck at what you do.
Not for my users. And there are enough of them out there that if there was some incredibly rare problem that only happened in 1/50000 installs, you would be getting a lot of complaints. Seriously, this is something that can be made bulletproof, if one cares to.
Unless your users are hundreds of kilometers in space and at risk of decompression from something going wrong, then no, your stuff is nowhere near as risky.
