One of the reasons it is so hard is because the discipline of thinking about those things isn’t baked into the language like it should be. You can’t look at a piece of code in a typical high-level language and reason about synchronization overhead because those semantics aren’t expressible in the code. We need languages that support expression of effects and coeffects, which would enable that kind of high-level reasoning about tradeoffs.
Do you have any ideas on what that would look like? The best I can come up with is something like https://seastar.io/ built in to the language.
But even that feels lacking, even though I'm really impressed with Seastar. I love the "bring operations to data" thinking.