I agree, and feel like Go was meant to solve problems Google had.

You have to explicitly pass and handle your own error stack, you can not have unused code, etc. It's such a pain to write and iterate in.

When I use Go, every weird thing eventually clicks into place when I imagine a first-year Google SWE writing it. It instills cultural values into compilation errors.

With Rust, all the weird things click into place, but in a way that feels empowering and not alienating. The x = match y { Ok(T) => {...}, None => {}} used to feel so alien and weird, but now it feels like a powerful incantation that all my thoughts can fit into.

There's this strange parallel. With Go, all the "clicks" were like the snapping of a bone. With Rust, all the "clicks" were like the popping of an estradiol bottle

You have to explicitly pass and handle your own error stack

this is gross lol

to be clear i have not done a lot of go and what i have done was mostly a year ago

this is because i did not like go

I think? You can just assign it to _ and it will be ignored, if you want. Like

val, _ := something()

ya, what i mean is, i think you gotta:

1. write val, err := something() and use err to build your own stack trace
2. make sure something() returns that err in the first place, if you wrote it

otherwise you don't get a stacktrace when something() fails.

i'm not confident about this, because i can't imagine Go reaching any acclaim while being so hilariously designed. but "Errors are values" so maybe we are right and go is bad

Oh, yeah. That's true. I have so much problems debugging go code because every crash is like, "the program the an unhandled error at like 123" and then you look at like 123 and it's like

if err := some_call() {
    panic("some_call failed!");
}

You just hid the stack trace that tells me what went wrong!!!

I much prefer Every Other Language, where you get a stack trace that runs into the library code!

something like

some_call() failed at call another_call(x, y, z)

another_call(x,y,z) failed at internal_library(x[123])

internal_library.c failed on line 1025: index 123 is out of bounds for array x

You can wrap your errors though, it's not hard to do. Use fmt.Errorf() but you have to actually do it. And people tend not to where I work.

Same situation! It's a bit more boilerplate on everything I write, but the main problem is not everyone does it.

Thankfully, now nobody writes Go at my work (^:

Unthankfully, we're language-shy because of it, lol