I find it useful to use the term "determinate" (determinacy) [1,2] when dealing with concurrent or parallel computing. That puts the focus on equality of outcome (same result), leaving open "deterministic" to mean the exact same sequence of events (schedule).
[1] As used by Jack Dennis and Arvind: <a href="https://cacm.acm.org/opinion/the-resurgence-of-parallelism/#body-4" rel="nofollow">https://cacm.acm.org/opinion/the-resurgence-of-parallelism/#...
[2] Originally defined by Karp & Miller: <a href="https://www.jstor.org/stable/2946247" rel="nofollow">https://www.jstor.org/stable/2946247
And it tracks with Determinate Systems, the Nix company. Nix is also focused on giving you the same results every time even if the build process is chaotic inside.
yvdriess · · focus · HN ↗
[1] As used by Jack Dennis and Arvind: <a href="https://cacm.acm.org/opinion/the-resurgence-of-parallelism/#body-4" rel="nofollow">https://cacm.acm.org/opinion/the-resurgence-of-parallelism/#... [2] Originally defined by Karp & Miller: <a href="https://www.jstor.org/stable/2946247" rel="nofollow">https://www.jstor.org/stable/2946247
tancop · · focus · HN ↗