An update on my "build your own async X in Rust" blog post series: I discovered something that I'm just too excited to share soon! 1/12
-
-
However, while researching how to teach those topics in an approachable manner, I kept reducing the complexity of async Rust until all that remained is something so simple I never thought was even possible... 3/12
Show this thread -
Imagine if the entirety of async-std, tokio, and mio fit into 1K lines of 100% safe code, with the same number of features and same performance! Here's why this is so important: 4/12
Show this thread -
When runtimes are so simple, the ability to build a best-in-class one is then not in the hands of a few concurrency experts anymore, but rather in everyone's hands. 5/12
Show this thread -
Furthermore, less complexity means fewer bugs, API easier to learn, and code that is easier to maintain and extend. 6/12
Show this thread -
Safe code inspires confidence. No need to anxiously test runtimes with thread sanitizer, miri, or loom. No need to even use those tools because safe code is immune to the kinds of bugs they catch! 7/12
Show this thread -
Don't worry about tunables because you can tune everything in a custom runtime. 8/12
Show this thread -
Because there is freedom to tune all the moving parts, you should be able outperform all other runtimes by yourself! 9/12
Show this thread -
If you look at how big the presently popular runtimes are, I want to reduce the complexity 10-20x in terms of lines of code and the size of API. 10/12
Show this thread -
I'm also excited to see more people building more async runtimes in Rust! I really think so far we've only been scratching the surface and there is so much yet to explore. 11/12
Show this thread -
Curious to hear thoughts and happy to answer questions! 12/12
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.