4 ms·

We're aiming for 1.0 by Q3 2020. I wrote a bit about it here: https://tokio.rs/blog/2019-11-tokio-0-2/#a-roadmap-to-1-0 https://tokio.rs/blog/2019-11-tokio-0-2/

We're aiming for 1.0 by Q3 2020. I wrote a bit about it here: https://tokio.rs/blog/2019-11-tokio-0-2/#a-roadmap-to-1-0 https://tokio.rs/blog/2019-11-tokio-0-2/#a-roadmap-to-1-0 That said, io_uring may end up impacting that target by a little bit. I understand the sentiment re v1. In reality, Tokio v0.1 was pretty much 1.0. We never cut 1.0 because async/await was in the works and it was unclear when it would be released. Now that async/await is out, 0.2 was a big change. We need some time to stabilize our APIs and collect user feedback. This process is happening now and going well.

carlmr 6y ago
As someone who has dabbled in Rust, I think the Rustaceans are just too careful to bump something up to v1 before it's near perfect. In other languages the package ecosystem looks more mature because people are less careful in bumping up numbers.
- carllerche 6y ago
  You aren't wrong. In hindsight, we should have shipped 1.0 a year or so after v0.1. I don't think we can ship 2.0 now. v0.3 is going to happen soon to fix errors in v0.2. async/await in Rust is very new. We are still figuring things out.
- naasking 6y ago
  I'm sure they look more mature, but they might leave a bad impression. Rust already has "bad PR" with the borrow checker, so libraries being more conservative before bumping versions might work in its favour. Otherwise you might get a bad impression from the language and apparently immature libraries.
  - larntz 6y ago
    For me the borrow checker is what I find interesting about rust. I wouldn't call it bad pr.
    - naasking 6y ago
      The people talking about it generally complain about it. Those comfortable with it generally aren't talking about it. I don't know what else to call that than bad PR. Just the nature of the beast.
michael_j_ward 6y ago
Have you discussed elsewhere about io_uring plans? It isn't mentioned at all in the linked roadmap
- carllerche 6y ago
  We are still figuring that out. When I wrote that post, uring was not yet working with sockets. Things have changed. We are exploring the space.
andrenth 6y ago
Is there anywhere I can read about the plans for io_uring integration?

carlmr 6y ago

As someone who has dabbled in Rust, I think the Rustaceans are just too careful to bump something up to v1 before it's near perfect. In other languages the package ecosystem looks more mature because people are less careful in bumping up numbers.

carllerche 6y ago
You aren't wrong. In hindsight, we should have shipped 1.0 a year or so after v0.1. I don't think we can ship 2.0 now. v0.3 is going to happen soon to fix errors in v0.2. async/await in Rust is very new. We are still figuring things out.
naasking 6y ago
I'm sure they look more mature, but they might leave a bad impression. Rust already has "bad PR" with the borrow checker, so libraries being more conservative before bumping versions might work in its favour. Otherwise you might get a bad impression from the language and apparently immature libraries.
- larntz 6y ago
  For me the borrow checker is what I find interesting about rust. I wouldn't call it bad pr.
  - naasking 6y ago
    The people talking about it generally complain about it. Those comfortable with it generally aren't talking about it. I don't know what else to call that than bad PR. Just the nature of the beast.

michael_j_ward 6y ago

Have you discussed elsewhere about io_uring plans? It isn't mentioned at all in the linked roadmap

carllerche 6y ago
We are still figuring that out. When I wrote that post, uring was not yet working with sockets. Things have changed. We are exploring the space.

andrenth 6y ago

Is there anywhere I can read about the plans for io_uring integration?