kskskuejej2

> I don't want to worry about every single exception when I am prototyping for example.

You are free to ignore the returned error, so for example to compare with a situation where you would raise an exception in another language inside a function, but not wrap the call in a try-catch:

val, _ := funcThatCanFail()

> Also, without stack traces, how do I know where an error comes from?

Go does have stack traces

And golang knows what type of error can be returned at compile time.

    type FatalError error
    func foo() FatalError {}

> Lack of exceptions

Go does support multiple return values, commonly (T, error). If you think about it for a while, you will realize a exception is just a type of return value.

Regarding generics, the more I used golang, the less I had a need for generics. Also, there is solutions if you insist, such as https://github.com/cheekybits/genny

Have you tried setting up LFS on your self-hosted ssh git repo?

Turns out LFS is designed to authenticate over https and doesn't work at all with ssh credentials out of the box because f* you.

I'm still hoping for a native git feature for large files, so the git-lfs crap can die in a fire.