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.
-
-
I keep yelling this on street corners and people just keep walking past me; occasional stink-eye.
-
Yeah, I’m *this* far away from entering “sir, this is a Wendy’s” mode
- 1 more reply
New conversation -
-
-
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.
-
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.
End of conversation
New conversation -
-
-
I have HTTP services serving thousands of requests per second per instance, doing non-trivial stuff with databases, all using regular threads and sockets (
iron, specifically) and it works great. There are use cases for async but they're probably pretty rare.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
can you expand on this?
-
You can use blocking i/o if it fits your program's economics.
- 3 more replies
New conversation -
-
-
Is there some sort of portable I/O readiness API in std::io that can be used to implement proper timeouts for blocking I/O? Something that thunks to e.g. poll(2) for the single-descriptor case, so you can wait readable/wait writable? Or is the answer to that the libc crate?
-
As far as I know there isn’t but (Libs team hat on) it sounds very good to add. Maybe the API is non-obvious enough that it could use an RFC for design discussion?
- 1 more reply
New conversation -
-
-
They scale well, but still they have a tighter limit than async, if you have more than about 255k requests at the same time, either a thread would fail, or the whole system may crash/panic, or you would make another instance which may mean extra communication code in some cases.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.