[1.Ch.] Orthocosmic Bullshit
The more I learn about Golang, the less I like it. Today I discovered that they decided pointers were worth preserving, but not pointer math.
Truly, Go is the Dark Souls of programming languages.
That's not a compliment.
[1.Ch.] Orrery Tries to Git Gud at Go
Latest complaint: https://tour.golang.org/moretypes/4
"To access the field X of a struct when we have the struct pointer p we could write (*p).X. However, that notation is cumbersome, so the language permits us instead to write just p.X, without the explicit dereference."
So, this tells me that if I see "foo.bar" in my code, I can't tell whether foo is a struct or a pointer until I check.
Somebody got paid for this.
[1.Ch.] Orrery Tries to Git Gud at Go
TIL that Go doesn't allow arrays to be resized. At all. If you want to make an array bigger, you have to make a new array and copy the contents of the old array into it. Exceeding the size of an array causes a runtime panic.
Really.
[1.Ch.] Orrery Tries to Git Gud at Go
And when I pointed this out to a coworkers, he told me that Go permits you to name variables in your function signatures, and that if you do, you can write a bareword "return" and Go will return the contents of the named variable to the calling routine.
That's somebody's future postmortem right there.
re: [1.Ch.] Orrery Tries to Git Gud at Go
@orrery Every time I see this cw I assume you're practicing Go, the classic game.
