Firefox

I’m sorry but I fail to see how these problems would be tied to having a long uptime (note the inline code block, as I mean the output of that command instead of uptime in an SLA, which is typically described as high or low instead of long or short). I have yet to find mentions where long uptime leads to higher chance of hardware failures as of recent. If some critical library or the kernel was removed some weeks prior to a reboot, I don’t think long or short uptimes would change your encounter of these issues.

And security patches are good, I agree. But there are instances where you don’t need it, eg in an airtight infrastructure, meant just for internal users, of which has no access to the Internet. You fall back to more traditional approaches to security in such cases.

As far as whether a service is properly restarted due to library updates, in a containerized environment, you wouldn’t have issues with library version mismatches, or missing libraries, or any sort of failure to restart due to dependencies getting changed without human attention (note that you can automate container updates, but you are then putting trust into whoever is publishing that container).

I’m not sure if it’s a lack of understanding of what my question is asking, or some other reason, but if you would please take the time to carefully read my questions and answer more appropriately and with clarity, that would be much appreciated.