News for hackers. Stuff that matters.
Re:Thoughts on Go vs. Rust vs. Zig by jpfromlondon on Friday December 05, 2025 @07:30AM (#46160401)
>it "just requires" you to flawlessly uphold memory access invariants manually across all possible concurrent states of your program.

The difference is it doesn't prevent you so it doesn't "just require"

Re:Thoughts on Go vs. Rust vs. Zig by kibwen on Friday December 05, 2025 @10:07AM (#46162260)
Sure, it only "just requires" it if you actually care about your program working properly in the presence of concurrency. To reiterate, this is as true in Rust as it is in C or Zig, it's just that also Rust allows you to do better than the "YOLO" approach to concurrency in a way that most languages could only dream of.

Seriously, I'm begging people to try writing a program that uses ordinary threads in Rust via `std::thread::scope`, it's eye-opening how lovely thread-based concurrency is when you have modern tools at your disposal.