Tokio: Runtime for writing reliable asynchronous applications with Rust

Re:Tokio: Runtime for writing reliable asynchronous applicat... by carlmr on Monday April 27, 2020 @06:07PM (#23000665)

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.

[ Parent | on HN ]

Re:Tokio: Runtime for writing reliable asynchronous applicat... by carllerche on Monday April 27, 2020 @06:16PM (#23000760)

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.

[ Parent | on HN ]

Re:Tokio: Runtime for writing reliable asynchronous applicat... by naasking on Monday April 27, 2020 @06:59PM (#23001171)

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.

[ Parent | on HN ]

Re:Tokio: Runtime for writing reliable asynchronous applicat... by larntz on Monday April 27, 2020 @07:41PM (#23001562)

For me the borrow checker is what I find interesting about rust.

I wouldn't call it bad pr.

[ Parent | on HN ]

Re:Tokio: Runtime for writing reliable asynchronous applicat... by naasking on Tuesday April 28, 2020 @12:08AM (#23003265)

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.

[ Parent | on HN ]