Just because the state of async I/O in Rust is not messy enough > “Romio is a fork of another Rust project called Tokio”https://github.com/withoutboats/romio …
-
-
Romio doesn’t look bad. But like all other similar projects, it will eventually be abandoned. The lesson here is that new languages should provide built-in async I/O, from day one. And stick to it. Even if it sucks. Give us a solid and stable base for a necessary feature.
Show this thread -
Go goroutines and channels may suck and not appear to be “the best solution”, are not “zero abstraction” and are not “safe”. But they work. They are stable. They are easy to understand. They have been around forever. They are good enough for most real-world problems.
Show this thread -
Nim’s AsyncDispath module isn’t bad either. It’s similar to what Rust is painfully trying to build, but has been driven by the willingness to solve real, rather than conceptual problems. Swift has the same issues as Rust, btw. Async I/O shouldn’t be an afterthought.
Show this thread
End of conversation
New conversation -
-
-
from the readme: "Romio is intended to unblock people trying to experiment with async/await"
-
today for "real world programming": use Tokyo. Simple. If you want to toy with async/await, you can play with romio.
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.