This article seems to break down into 3 parts - why multiple return values are bad, why go error handling is bad, and opinions about what to do about it.
The part that feels wrong to me is their issue with multiple return values. They argue that multiple return values are a special case in the type system, so they don't compose well. But, as far as I can figure, function arguments are also a special case, in the exact same way. I think if the author wants to argue go should only have one return value, then use tuple destructuring to simulate multiple return values, they should also argue functions should only take one argument, and use tuple destructuring to break it apart within the function.
I don't think having a special case for either the input or output of a function is particularly weird, and I can't think of any language (except haskell?) that limits you to one argument.
I don't know. I don't think they're particularly wrong about multiple return types being ugly, but it also doesn't feel like some great tragedy to me the way it does to the author.
Eg - fundraise to cover the cost of producing the movie and paying the salaries of everyone involved, because physically making a movie costs money. Then give the mp4 away for free because copying a digital file costs nothing. Piracy is only a problem because companies are trying to charge money for copying a file, which is fundamentally free.
I was wondering why the GCC Machine Description language was such an outlier, especially considering I've never heard of it before. I googled it, and it turns on machine description files use the extension ".md".
Epic bought artstation, bandcamp, and, sketchfab. I don't know for sure, but I don't think any of those are very profitable. They're almost like resume hosting websites for game developers. 3d artists show off their work on sketchfab, artists show off on artstation, musicians show off their work on bandcamp.
My impression is that epic bought them for sort of the same reason Microsoft bought linkedin. They don't make tons of money, but they enhance the pipeline of artists and musicians available to the game industry.
Of course I have no idea if that's why they did it, but epic has definitely shown interest in steering the direction of the game industry in the past, and aligning the talent pool with their way of thinking is maybe a good way to do that.
The part that feels wrong to me is their issue with multiple return values. They argue that multiple return values are a special case in the type system, so they don't compose well. But, as far as I can figure, function arguments are also a special case, in the exact same way. I think if the author wants to argue go should only have one return value, then use tuple destructuring to simulate multiple return values, they should also argue functions should only take one argument, and use tuple destructuring to break it apart within the function.
I don't think having a special case for either the input or output of a function is particularly weird, and I can't think of any language (except haskell?) that limits you to one argument.
I don't know. I don't think they're particularly wrong about multiple return types being ugly, but it also doesn't feel like some great tragedy to me the way it does to the author.