Great talk! Hope I will understand Tokio better in the near future. Futures are cool, but using Tokio just feels like abstracting everything as a stream.
A key difference is that Futures don’t automatically start when they are created. They start when await is applied to them. JS Promises start when they are created.
Not sure what you mean by "just"--most languages have a "future-like" scheme of some sort for async, the point is building the right version of that in rust with the language's goals in mind. Tokio may do a similar thing to python twisted, but given that it's written in rust, it's significantly faster and provides all the great guarantees that rust does--memory safety, safe concurrency, etc etc.
More like Python's asyncio at least as far as the API goes. Twisted is just callback hell, a bit like JS Promises. They're all forms of async programming, but not all async techniques are created equal.
![ค้างคืนโรงเก็บกระสวยอวกาศร้างกลางทะเลทราย [Around The World Ep. 3]](http://i.ytimg.com/vi/E5bWZQhABJE/mqdefault.jpg)
![[Full] 4 ต่อ 4 Celebrity EP.920 | 3 พ.ย. 67 | one31](http://i.ytimg.com/vi/KwiW2M_kAg4/mqdefault.jpg)
Disappointed that the talk is not call Fast and Asynchronous: Tokio Drift. But awesome talk, thanks.
I'm disappointed that it wasn't called: You Can't Spell Rust Fest Without Futures
I always enjoy talks by Alex Crichton. Very professional and knowledgeable guy. Thanks for sharing!
Yes but the pacing is very jittery.
This is more informative than tokio documentations
Great talk! Hope I will understand Tokio better in the near future. Futures are cool, but using Tokio just feels like abstracting everything as a stream.
Futures looks similar to Promise in JS to me
A key difference is that Futures don’t automatically start when they are created. They start when await is applied to them. JS Promises start when they are created.
Why isn't anyone using constructive/destructive interference to fix these large hall reverberations?
Biff gives sports almanac to himself in the past.
Not his father.
Nice Presentation BTW :)
We'll make sure that we improve our meme and retro movie training. Alex will have to take it again.
@@RustVideos How can I now trust anything he said if he makes a mistake IN THE MOST SUBSTANTIAL IMPACTFUL SUBJECT!!!!!!!!!.
Could someone enlighten me ... isn't this just Python Twisted for Rust?
Not sure what you mean by "just"--most languages have a "future-like" scheme of some sort for async, the point is building the right version of that in rust with the language's goals in mind. Tokio may do a similar thing to python twisted, but given that it's written in rust, it's significantly faster and provides all the great guarantees that rust does--memory safety, safe concurrency, etc etc.
not to mention that Python's queue was not thread-safe before a recent patch....
More like Python's asyncio at least as far as the API goes. Twisted is just callback hell, a bit like JS Promises. They're all forms of async programming, but not all async techniques are created equal.