I have reached the part of my rust journey where I just.. need tokio. I have a bad feeling about this whole thing
-
Show this thread
-
This Tweet is unavailable.
-
-
nothing, alex just made sure I can't complain about stuff without feeling bad anymore well played alex
3 replies 0 retweets 4 likes -
Replying to @fasterthanlime @myrrlyn
so fair warning that my perspective might be biased a bit (as a relatively frequent tokio contributor), but i honestly think tokio is perhaps the best asynchronous programming experience i have had in any language
1 reply 0 retweets 2 likes -
it is worth noting that asynchrony inherently is hard (cf. my twitter header image) and you probably don't want to be asynchronous unless you *need* to be asynchronous, but it makes me kind of sad how people tend to notice this but interpret it as "tokio sucks and is hard"
1 reply 0 retweets 1 like
Async is hard, but I am having a tougher time starting out with async Rust - overall a lot of confusion between old Futures, new Futures, async/await, what is compatible with what... Having some established starting points/a learning path would ease the journey considerably.
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.
Writing about stuff to learn how it works, mostly in Rust.
Lead Engineer at