I occasionally program Go because it has an amazing amount of libraries - I basically use it for random microservice type things that glue systems together. (Mo

I occasionally program Go because it has an amazing amount of libraries - I basically use it for random microservice type things that glue systems together. (Most recently, an HTTP login endpoint that sends and receives XMPP messages to authenticate the user.) I don't like it. I program Rust the rest of the time. I'm considering learning Perl5 so that at least my type system lets me do vaguely expressive things - I'm utterly fed up of half my code looking like: foo, err := something() if err != nil { return nil, someErr{err} } I got very used to Rust's try!() macro, now ? operator, and being able to map over Results to convert between error types in a single line that feels much less noisy - I have functions in Go that are a dozen or so lines that would've been 3 in Rust, and tbh I struggle to follow what the function actually does when 3 out of 4 lines are to do with the failure case. I would consider "unacceptably crippled" to be a reasonable description of Go, even if it's the best tool I have for some jobs.