3 ms·
That's not necessarily a "low" standard. It's that the value of preventing a reboot every few days is much lower than other things we could spend our time on. M
by AuthorizedCust 7y ago
That's not necessarily a "low" standard. It's that the value of preventing a reboot every few days is much lower than other things we could spend our time on. Mandatory oftware perfection would be a huge drag on valuable new features.
- pcurve 7y agoI agree with you to a certain degree but appropriateness of the trade off should really depend on where the software is used. Airplane, powerplants, and train signaling systems? I would want longer uptime.
- cm2187 7y agoEspecially when you compare that to all the other maintenance that has to happen routinely on a plane for it to remain safe. Not a reason to not fix it though.
- 420codebro 7y agoExcuse me for this: But that is a heinously horseshit answer. This isn't some app on your iPhone to find someone to fuck. We are talking about an airliner with many souls on board. Taking extra time to prevent a periodic reboot due to an unexplained / unresolved issue is the norm in these use cases (life critical systems). Please don't ever work on anything life critical - your attitude is completely incompatible.