I’ve never understood the “async I/O is too complicated, why can’t we just use goroutines?” criticism of Rust. You can! They’re called threads, and they work great.
-
-
An extra context switch? They do less kernel context switches because the scheduler is in userland. And I don't really see OS thread creation as equivalent to pulling a stack from a userland allocator. Obv moving stacks is... interesting without some GCish infrastructure.
-
All said, I'm sure the issues with networking stuff in Rust are more along the "why doesn't any of this stuff exist in some simple form under a standard or defacto standard API" moreso than any particular implementation choices.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.