News for hackers. Stuff that matters.
Re:Tokio 1.0 – async runtime for Rust by Xevi on Wednesday December 23, 2020 @05:59PM (#25523279)
Woah, I didn't know about that. Does this mean Rust only has one maintained runtime now? Namely Tokio.
Re:Tokio 1.0 – async runtime for Rust by FridgeSeal on Wednesday December 23, 2020 @06:38PM (#25523562)
Async-std is still actively maintained and developed.
Re:Tokio 1.0 – async runtime for Rust by Xevi on Wednesday December 23, 2020 @08:03PM (#25524131)
I was under the impression that it's based on Smol, but maybe I'm wrong.
Re:Tokio 1.0 – async runtime for Rust by nicoburns on Wednesday December 23, 2020 @08:16PM (#25524212)
It has separate maintainers (a whole team), who will continue to maintain the parts of smol they are using. Smol is relatively small and sinple.
Re:Tokio 1.0 – async runtime for Rust by sanxiyn on Wednesday December 23, 2020 @06:17PM (#25523411)
I think it's rather that smol is "complete" and doesn't need much maintenance.
Re:Tokio 1.0 – async runtime for Rust by Xevi on Wednesday December 23, 2020 @08:05PM (#25524149)
Maybe that's true. I don't know how complex these things are, or if they will be affected by future changes in the language, but it feels weird to say that a critical piece of software is complete. I wonder if many new libraries will use Smol.
Re:Tokio 1.0 – async runtime for Rust by gpm on Wednesday December 23, 2020 @10:40PM (#25524841)
One of the principles that stjepang was very keen on for smol was that libraries shouldn't depend on it. Libraries should be written in an async-executor generic way and the end binary should then be free to use smol as the executor, or tokio, or anything else.

I'm currently using smol (in an application I'm developing - not just a library) and I don't think this will scare me away. He appears to still be responding to pull requests, and smol consists of a reasonably small amount of very high quality code.