Thoughts on Go vs. Rust vs. Zig

Re:Thoughts on Go vs. Rust vs. Zig by oncallthrow on Thursday December 04, 2025 @06:24PM (#46154672)

> the exception thrown on failure will not only contain the reason, but the filename and the whole backtrace to the line where the error occurred.

... with no other context whatsoever, so you can't glean any information about the call stack that led to the exception.

Exceptions are really a whole different kettle of fish (and in my opinion are just strictly worse than even the worst errors-as-values implementations).

[ Parent | on HN ]

Re:Thoughts on Go vs. Rust vs. Zig by reissbaker on Thursday December 04, 2025 @06:41PM (#46154877)

Your Go example included zero information that Python wouldn't give you out-of-the-box. And FWIW, since this is "Go vs Rust vs Zig," both Rust and Zig allow for much more elegant handling than Go, while similarly forcing you to make sure your call succeeded before continuing.

[ Parent | on HN ]