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.
Here's another article just for you:
Proc macro support in rust-analyzer for nightly rustc versions
I don’t mean to complain. Doing software engineering for a living is a situation of extreme privilege. But there’s something to be said about how alienating it can be at times.
Once, just once, I want to be able to answer someone’s “what are you working on?” question with “see that house? it wasn’t there last year. I built that”.
Instead for now, I have to answer with: “well you see… support for proc macros was broken in rust-analyzer for folks who used a nightly rustc toolchain, due to incompatibilities in the bridge (which is an unstable interface in the first place), and it’s bound to stay broken for the foreseeable future, not specifically because of technical challenges, but mostly because of human and organizational challenges, and I think I’ve found a way forward that will benefit everyone.”