News for hackers. Stuff that matters.

A comment on Tokio 1.0 – async runtime for Rust. Parent comment

Re:Tokio 1.0 – async runtime for Rust by lucacasonato on Wednesday December 23, 2020 @02:32PM (#25521197)
Yes, Deno uses it as its internal event loop for JS code.
[ Parent | on HN ]
Re:Tokio 1.0 – async runtime for Rust by steveklabnik on Wednesday December 23, 2020 @02:39PM (#25521278)
Fun party fact: long ago, Rust had libuv built in too.
[ Parent | on HN ]
Re:Tokio 1.0 – async runtime for Rust by shepmaster on Wednesday December 23, 2020 @02:47PM (#25521372)
... for not-so-fun parties. ;-)
[ Parent | on HN ]
Re:Tokio 1.0 – async runtime for Rust by p5a0u9l on Wednesday December 23, 2020 @03:56PM (#25522129)
why’d they move past it? does libuv not fit well in rust?
[ Parent | on HN ]
Re:Tokio 1.0 – async runtime for Rust by creata on Wednesday December 23, 2020 @04:05PM (#25522226)
Rust used to have a lot of stuff built into the language, including garbage collection![0] I think that a long time ago they chose to move stuff out into libraries so that Rust could be a serious competitor to C++.

https://pcwalton.github.io/2013/06/02/removing-garbage-colle...

[ Parent | on HN ]
Re:Tokio 1.0 – async runtime for Rust by steveklabnik on Wednesday December 23, 2020 @03:59PM (#25522158)
Back then, Rust had a built-in runtime. It was removed, and libuv with it.
[ Parent | on HN ]