Comparing Exceptions and Errors

[Ola Fosheim Grøstad]

On Sunday, 5 June 2022 at 00:18:43 UTC, Adam Ruppe wrote:
> Run it in a separate process with minimum shared memory.

That is a workaround that makes other languages more attractive. 
It does not work when I want to have 1000+ actors in my game 
server (which at this point most likely will be written in Go, 
sadly).

So a separate process is basically a non-solution. At this point 
Go seems to be the best technology of all the bad options! A 
pity, as it is not an enjoyable language IMO, but the goals are 
more important than the means…

The problem here is that people are running an argument as if 
most D software is control-software for chemical processes or 
database kernels. Then people quote writings on safety measures 
that has been evolved in the context/mindset of control-software 
in the 80s and 90s. And that makes no sense, when only Funkwerk 
(and possibly 1 or 2 others) write such software in D.

The reality is, most languages call C-libraries and have C-code 
in their runtime, under the assumption that those C-libaries and 
runtimes have been hardened and proven to be reliable with low 
probability of failure.

*Correctness **is** probabilistic.* Even in the case of 100% 
verified code, as there is a possibility that the spec is wrong.

*Reliability measures are dependent on the used context*. What 
«reliable» means depends on skilled judgment utilized to evaluate 
the software in the use context. «reliable» is not a context 
independent absolute.