Post

@steveklabnik.com Coming from mostly Python based async (Twisted, and some amount of asyncio) I found this essay https://without.boats/blog/why-async-rust/ to really help explain some of the OTHER stuff around async in Rust (beyond I/O). The origin-story helped me 😀 Overall I've found tokio and […]

yeah boats' writing is really good

i wonder if the current Futures, etc abstractions/traits in Core need a rethink to support io_uring , although i think that's still disabled for security reasons in Android/ChromeOS, so maybe it's not as relevant out-in-the-wild as some noisy folks would suggest?

Is there a bit of subtext here pointing toward a social consequence of abstraction (in the “information hiding” sense)? That is there’s room to bikeshed/complain since the the explicit aim is hide details that one would otherwise use to have a more nuanced discussion?

Great article - and as a pony developer I hear the "I don't want a runtime" line a *lot*. An actor based model has to have schedulers and a runtime. Question about this: "No ifs or buts, no attempt to sneak in garbage collecting or refcounting through the backdoor while no one is looking".

I don't know rust well, but as I understand it - isn't Arc used for sharing across. threads? Which I thought was reference counted, and garbage collected?