RustFest Zürich 2017 - Tokio: How we hit 88mph by Alex Crichton

Ғылым және технология

Async I/O has forever been a hot topic of discussion in Rust, but over the past year we’ve seen some significant advances in this domain with the futures crate an the Tokio project. We’ll start off by taking a look at where we are today with the async I/O ecosystem in Rust, highlighting a number of the features we’ve added in both the libraries and the language over the past year. We’ll then take a deep dive into Tokio itself, seeing how it capitalizes on some of Rust’s greatest strengths by going Back to Futures and gets our DeLorean up to 88mph.
About Alex Crichton:
Alex is a member of the Rust Core Team who has worked at Mozilla on Rust for the past four years. He is also a member of the Tokio Core Team, one of the primary authors of Cargo, helps maintain the standard library, and likes to ensure that engine of Rust never stops.

Пікірлер: 17

  • @kidcoder5359
    @kidcoder53596 жыл бұрын

    Disappointed that the talk is not call Fast and Asynchronous: Tokio Drift. But awesome talk, thanks.

  • @jonarmani8654

    @jonarmani8654

    3 жыл бұрын

    I'm disappointed that it wasn't called: You Can't Spell Rust Fest Without Futures

  • @splittydev
    @splittydev6 жыл бұрын

    I always enjoy talks by Alex Crichton. Very professional and knowledgeable guy. Thanks for sharing!

  • @PaulSebastianM

    @PaulSebastianM

    5 жыл бұрын

    Yes but the pacing is very jittery.

  • @aiman_yt
    @aiman_yt6 жыл бұрын

    This is more informative than tokio documentations

  • @TheOMGPoPCorn
    @TheOMGPoPCorn5 жыл бұрын

    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.

  • @PaulSebastianM
    @PaulSebastianM5 жыл бұрын

    Why isn't anyone using constructive/destructive interference to fix these large hall reverberations?

  • @qhkmdev
    @qhkmdev4 жыл бұрын

    Futures looks similar to Promise in JS to me

  • @MarkVolkmann

    @MarkVolkmann

    3 жыл бұрын

    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.

  • @dmitrij34
    @dmitrij346 жыл бұрын

    Biff gives sports almanac to himself in the past. Not his father.

  • @dmitrij34

    @dmitrij34

    6 жыл бұрын

    Nice Presentation BTW :)

  • @RustVideos

    @RustVideos

    6 жыл бұрын

    We'll make sure that we improve our meme and retro movie training. Alex will have to take it again.

  • @blackwhattack

    @blackwhattack

    5 жыл бұрын

    @@RustVideos How can I now trust anything he said if he makes a mistake IN THE MOST SUBSTANTIAL IMPACTFUL SUBJECT!!!!!!!!!.

  • @pm71241
    @pm712416 жыл бұрын

    Could someone enlighten me ... isn't this just Python Twisted for Rust?

  • @GrayOlson

    @GrayOlson

    6 жыл бұрын

    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.

  • @ac130kz

    @ac130kz

    5 жыл бұрын

    not to mention that Python's queue was not thread-safe before a recent patch....

  • @peter9477

    @peter9477

    6 ай бұрын

    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.

Келесі