Async Rust doesn't have to be hard
I learned Rust by writing a (fuse-based) filesystem [0]...about 30k lines iirc. Rust was challenging, but not crazy difficult (it helps that I have a C++ background). I loved it. Development was slower than a dynamic language, but faster than C++, and most importantly, I felt <i>safe.</i> It&#x27;s a really solid language.<p>However, when I took a look at async Rust, it really did appear to be a mess. I have substantial experience with Python async&#x2F;await (which is also a mess), so I&#x27;m not unfamiliar with the async concepts. Honestly, I think it&#x27;s the idea of an event loop in a compiled + non-memory-managed language. You really have to think hard about where objects are living and for how long, and combine that with the illusory world of how async&#x2F;await appears to work (versus how it actually works), it gets hard to conceptualize. Maybe I just didn&#x27;t spend enough time with it to feel comfortable with it, but that&#x27;s my hot take.<p>Imo, Go does performant concurrency right. Rust would be smart to adopt what Go offers.<p>0. <a href="https:&#x2F;&#x2F;github.com&#x2F;amoffat&#x2F;supertag" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;amoffat&#x2F;supertag</a>