Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

All the ecosystem is using Tokio and async for web stuff. I agree for those cases go is much saner.


My point was that you can program in Rust in the exactly same style as Go, not hitting any of the problems mentioned in the linked article. Just use tokio::spawn and tokio channels and you get all the stuff you have in go.

And btw, I just did that recently - I ported a proxy written in Go to Rust and actually it turned out to be simpler than the original thanks to things like join!, select!, RAII, being able to return a value from an async call easily.


If you have any pieces of code you can share, I'd be interested in seeing what Go code looks like in equivalent Rust with tokio.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: