At some point get around to writing a longer post about why I don't really like jj/jujutsu. But at least it turns out it's at least pretty easy to block it from my repositories.

So, we've covered polling. We've tackled sleeping (and waking). Going back to the definition, that leaves us with one core concept left to conquer: pinning!

So. You've read my last post. You got inspired. Excited, even. Deployed SimpleFuture to production. Spun up a few worker threads to share the load. Called it a friday. This is Rust after all, what could go wrong?

...aaand then someone took a look at the CPU usage.

There are a lot of guides about how to use async Rust from a "user's perspective", but I think it's also worth understanding how it works, what those async blocks actually mean.

Why you get all those weird pinning errors.

Well, I just picked up this game called Wanderstop. Or, well, picked it up a few days ago, but I just finally got around to finishing the prologue, stopped crying, and felt like I had to go write.

Beware of spoilers for the tutorial below the fold. Wait, can tutorials have spoilers? Does that even make sense? Is calling it out as a spoiler a spoiler in itself? What about when the same things are said on the store page?