164
Go vs Rust learning (programming.dev)
submitted 4 months ago by [email protected] to c/[email protected]
28 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[-] [email protected] 63 points 4 months ago* (last edited 4 months ago)

Go is like that abusive partner that gives you flowers and the next day makes you feel like shit. Then another day you go to an expensive restaurant and you tell yourself that maybe it's not so bad and they still care. And the cycle continues.

Rust is an autistic partner that sometimes struggles with telling you how much they care, is often overly pedantic about technical correctness and easily gets sidetracked by details, but with some genuine effort from both sides it's very much a workable relationship.

[-] [email protected] 43 points 4 months ago

Yeah but Go has the best error handling paradigm of any programming language ever created:

ret, err := do_thing()

if err != nil {
    return nil, err
}

Don't you just love doing that every 5 lines of code?

[-] [email protected] 6 points 4 months ago

I actually reasonably like Go. It's simple and pragmatic but I fucking loathe its error handling. To me it just replicates one of the worst features of C

[-] [email protected] 4 points 4 months ago

I don't like the rust way either. But at least you can unwrap

[-] [email protected] 20 points 4 months ago

With some sprinkle of libraries such as anyhow and thiserror the Rust errors become actually pleasant to use. The vanilla way is indeed painful when you start handling more than one type of error at a time.

[-] [email protected] 5 points 4 months ago

Exactly this. Anyhow makes error handling in rust actually a joy. It's only something you need to consider if you're writing a library for others to use, and in that case, it's good that rust forces you to be very very explicit

[-] [email protected] 4 points 4 months ago* (last edited 4 months ago)

I do think Zig is better for this kind of thing.

const ret = try do_thing();

if( ret ) | result | {
   do_something_with_result(result);
}

The try keyword returns any error up; the if-unwrap works with what came out of a successful call. Normally you wouldn’t have both, of course.

do_thing would be defined as a union of an error (a distinct kind of type, so it can be reasoned about with try, catch and unwrapping) and the wrapped return value.

[-] [email protected] 5 points 4 months ago

That syntax looks atrocious

[-] [email protected] 2 points 4 months ago

Well, different floats for different boats I suppose.

[-] [email protected] 2 points 4 months ago

Honestly, I do

[-] [email protected] -1 points 4 months ago

It's not pretty, but it's uniform, obvious, and easy to understand.

go is good grug friend who chase away complexity demon by limit damage of big brain developer

this post was submitted on 15 May 2024
164 points (84.5% liked)

Programmer Humor

19274 readers
596 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]