4 ms·
These discussions happen when people don’t give consideration to the fact that reliability is an architectural concern and error handling is part of that. Ther
by blub 4y ago
These discussions happen when people don’t give consideration to the fact that reliability is an architectural concern and error handling is part of that.
There’s certainly a minimum of error handling that has to be done in order for code to be considered generally correct, but a lot also depends on the reliability requirements.
Sometimes it’s just inappropriate to abort and this may deeply change the architecture of a program, including by making hard demands on the toolchain, hardware and OS.
- tsimionescu 4y agoCompletely agree. Even with "fail fast", there are many levels where this makes sense - for example, you may not want to let an entire server application crash just because one request couldn't be successfully served; but you may still design it to crash and restart for other conditions, rather than trying to recover from more serious errors.