News for hackers. Stuff that matters.

A comment on Thoughts on Go vs. Rust vs. Zig. Parent comment

Re:Thoughts on Go vs. Rust vs. Zig by ViewTrick1002 on Friday December 05, 2025 @02:43AM (#46157749)
Given the constraints I still haven’t seen an asynchronous proposal for Rust that would do things differently.

Keep in mind that one requirement is being able to create things like Embassy.

https://github.com/embassy-rs/embassy

[ Parent | on HN ]
Re:Thoughts on Go vs. Rust vs. Zig by afiori on Friday December 05, 2025 @04:05AM (#46158464)
I agree, I think they should have delayed it.

In a different universe rust still does not have async and in 5 years it might get an ocaml-style effect system.

[ Parent | on HN ]
Re:Thoughts on Go vs. Rust vs. Zig by ViewTrick1002 on Friday December 05, 2025 @04:22AM (#46158822)
And in that universe Rust is likely an inconsequential niche language.
[ Parent | on HN ]
Re:Thoughts on Go vs. Rust vs. Zig by afiori on Friday December 05, 2025 @08:21AM (#46160912)
If rust skipped async features I think it would not have damaged it much
[ Parent | on HN ]
Re:Thoughts on Go vs. Rust vs. Zig by ViewTrick1002 on Friday December 05, 2025 @10:23AM (#46162476)
Almost the entire early large scale adoption came from people writing async web services.

From 2023:

> In that regard, async/await has been phenomenally successful. Many of the most prominent sponsors of the Rust Foundation, especially those who pay developers, depend on async/await to write high performance network services in Rust as one of their primary use cases that justify their funding.

https://without.boats/blog/why-async-rust/

[ Parent | on HN ]