5 ms·
I thought the author's point was relatively clear: Rust might not be a good fit for the kind of tasks that need more concurrency than raw threads can give you.
by nemetroid 3y ago
I thought the author's point was relatively clear: Rust might not be a good fit for the kind of tasks that need more concurrency than raw threads can give you. Such programs should be written in some other language instead.
> Maybe Rust isn’t a good tool for massively concurrent, userspace software. We can save it for the 99% of our projects that don’t have to be.
- hot_gril 3y agoSo 99% of projects need raw threads only, according to the author. I doubt that.
- nemetroid 3y agoIt sounds very reasonable to me. I would say 90% of programs don’t need threads or concurrency at all.
- hot_gril 3y agoAnything that waits on I/O needs concurrency (but not necessarily threads). Web backends, web frontends, deeper backends, desktop GUIs, that's probably 90% of software right there.