Who Runs Your Rust Future? Hands-On Intro to Async Rust

> What is harder to find is the bridge between them, the part that connects understanding how async works to actually shipping with it.

There is actually already a tutorial at this level: Tokio has its ‘async in depth’ tutorial [1] that walks you through building a toy runtime and using it to run a future.

Not a complaint — you can never have too many tutorials, unless they're about monads — but just a pointer in case you hadn't seen it :)

[1]: https://tokio.rs/tokio/tutorial/async

▲

Havoc an hour ago | parent | prev | next [-]

Bit weird to have a rust tutorial list JavaScript async as assumed knowledge tbh.

▲

uxns 2 hours ago | parent | prev | next [-]

With so much AI-produced junk out there, sites like this one are a breath of fresh air. Simple, aesthetic with real educational value. A second place this week (after https://www.makingsoftware.com/) where I've happily parked a few hours of my life.

▲

vanillameow 3 hours ago | parent | prev | next [-]

I really enjoy the prose of this article. The writing breaks down concepts in a very easily understandable way. Thank you for posting, will definitely finish this one later!

▲

Quarrel 3 hours ago | parent | prev | next [-]

I liked this article because it helped me understand the javacript engine flow better than I had.

The rust flow is so much more natural to me.

▲

amelius 2 hours ago | parent | prev [-]

Don't use async but use threads instead. Threading treats the CPU as a resource, which it is! Whereas async simply locks the CPU, which can deplete the system for longer computations.

If you hate garbage collection pauses (which most Rust users do) then don't use async.

	▲	himata4113 2 hours ago \| parent \| next [-]
		You use async to preserve system resources. For example you can easily exhaust the host with ~20k connections running a thread-per-connection schema where each thread simply waits for epoll event, async prevents this by having a threadpool of ~16 threads that handle all the connections instead of polling the scheduler wakes it up, asks "do you haev work to do" if not continues to next task. (This heavily varied by the async runtime implementation, each async runtime can and will act differently to maximize efficiency over throughput)
	▲	inigyou an hour ago \| parent \| prev \| next [-]
		They are two different models and sometimes one is better than the other. Async tends to win for IO-bound code (due to using less memory for each blocked coroutine) and threads for CPU-bound code.
	▲	toprerules 2 hours ago \| parent \| prev [-]
		Your confusing concurrency with parallelism. Async allows one core to switch between many threads of execution that can do work and not stop one thread of execution because it needs to wait for a resource. It's beneficial to use async if you're application is I/O heavy even if it's single threaded. > Whereas async simply locks the CPUWhereas async simply locks the CPU This is also completely nonsense, context switching behavior is OS dependent and your average general purpose kernel is not cooperative. You will run for your allotted quanta or reschedule when you run out of coroutines that can execute without waiting for resources.