I'm sympathetic to this point but I think that: a) Saying Node + Deno are good is a stretch. Node has horrible performance, even for simple routing. And I'll s

I'm sympathetic to this point but I think that: a) Saying Node + Deno are good is a stretch. Node has horrible performance, even for simple routing. And I'll source that[0]. b) Saying that adding `Send + Sync + 'static` bounds is a serious burden is, to me, overstating things. > the far better model for writing performant servers. It's completely workload dependent. For a chat server it's almost definitely not going to be more performant and you may end up with worse latency. > it only costs you friction everywhere else in your entire codebase, and quite often performance as well. I am unconvinced tbh. I do not believe that adding Send + Sync + 'static bounds is onerous, I do not believe satisfying those bounds is hard (it's almost always just a matter of moving the value), and I do not believe that the vast majority of programs benefit from TPC architecture. I recognize that there is a problem here - that we are optimizing for one runtime at the expense of others - but I am not convinced at this point that the problem matters. [0] https://www.techempower.com/benchmarks/#section=data-r21&test=json https://www.techempower.com/benchmarks/#section=data-r21&tes...