Re: "It solves a problem that people have."
Just imagine engineers saying "All bridges collapse" and just sort of accepting that under normal everyday circumstances a bridge might fall down. All software does not crash. Well written software will deal with known and unknown circumstances. Occasionally, yes, something weird might happen. At that point you want your system to fail to another host or stop, not just restart and hope for the best. We don't rebuild bridges to the same spec during a hurricane because we know the new one would break immediately. A crash should be your warning that something is very, very wrong and unusual. I'd almost suggest that instead of restarting the service a system ought to keep a record on a three strikes principle - if software crashes three times, permanently block it from running to force a real solution to the problem!
Biting the hand that feeds IT
