There really needs to be some kind of FAQ entry that we can link to to answer the “why not just use CSP? Have you read ‘what color is your function?’” question that comes up anytime anyone posts anything about async I/O in Rust. This is getting ridiculous.
-
Show this thread
-
I think one of the biggest misconceptions about Rust, which possibly comes from Node, is that you *have* to use async I/O for usable I/O. Not true! You can use 1:1 threads or M:N threads (mioco) if you want, and they scale well. No red or blue functions in sight.
8 replies 4 retweets 50 likesShow this thread -
Replying to @pcwalton
I keep hearing folks bring up perf arguments for async/await, but I wish the narrative would focus on portability instead. With async/await we can now write async code that works natively and in browsers, without worrying about they're executed.
1 reply 0 retweets 10 likes
For example with timers: almost everyone just wants to schedule a timeout. Few people want to worry about the details of *how* this is achieved (dedicated timer thread on native, SetTimeout in browsers). Having a single API able to front both impls feels incredibly liberating.
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.