How can you support me?
All of the articles, videos, and open source contributions that are made here are funded directly by individuals and companies through donations.
- GitHub Sponsors is based in the US, pays through Stripe
- Patreon has the highest fees, but it’s here too out of convenience.
The “Silver” tier gives you advance access to articles and videos, one week before they’re made available to everyone else. Every piece of content ends up publicly available eventually — I consider my work a public service.
For those who cannot afford to pitch in financially, you can still help:
- Follow me on Bluesky or Mastodon
- Subscribe to my YouTube channel
- Subscribe to my RSS feed
- Send me good vibes by e-mail
I’m extremely lucky to be able to contribute to the Rust ecosystem as an independent, and can only do it through the support of people like you.
Thank you so much for your continued support, I owe y’all everything.
Did you know I also make videos? Check them out on YouTube!
Here's another article just for you:
Getting in and out of trouble with Rust futures
I started experimenting with asynchronous Rust code back when futures 0.1
was all we had - before async/await. I was a Rust baby then (I’m at least
a toddler now), so I quickly drowned in a sea of .and_then, .map_err
and Either<A, B>.
But that’s all in the past! I guess!
Now everything is fine, and things go smoothly. For the most part. But even
with async/await, there are still some cases where the compiler diagnostics are,
just, so much.