Thread-per-core
I&#x27;ve never touched Rust, but I can see the complaint -- if I have to write my code in a special way so that its state can be marshalled across threads to redistribute load in a way that I do not need and will make the actual end-to-end latency of a single request actually <i>slower</i> in cases where I&#x27;ve got oodles of CPU head-room, I would find that infuriating.<p>I could see this approach making sense in a platform where transferrable state was the default and is rarely broken, but it doesn&#x27;t sound like that&#x27;s the case in Rust?<p>edit: I&#x27;m curious, what&#x27;s the ergonomics like for this?  Is it just &quot;oh, your code won&#x27;t compile if you don&#x27;t add this magic incantation to say it has `Send`?&quot;  Or is it &quot;your code will fail in intermittent, hard-to-debug ways as state gets mangled during work-steals if you don&#x27;t do this right&quot;?