Re:Notes on structured concurrency, or: Go statement conside...
by masklinn on Saturday July 02, 2022 @11:08AM
(#31959656)
> So we should not think about it first, just do it?
It is much easier to bake concurrency and parallelism from the start than to retrofit it in an existing sequential project, even more so as it avoids sub-optimal patterns.
> And not consider whether there are better solutions such as checking we're using the right algos or cache-aligning our accesses or using a probabilistic filter before hitting the DB or..
Why are you declaring that those are incompatible with concurrent programs, exactly?
It is much easier to bake concurrency and parallelism from the start than to retrofit it in an existing sequential project, even more so as it avoids sub-optimal patterns.
> And not consider whether there are better solutions such as checking we're using the right algos or cache-aligning our accesses or using a probabilistic filter before hitting the DB or..
Why are you declaring that those are incompatible with concurrent programs, exactly?