I use Go quite a lot, and I agree with their "irrational arguments". It seems quite dishonest to pretend that anyone who doesn't use Go because they found it too restrictive to be "wasting their time with irrational stances". It's also quite close-minded.
You're right that most Go developers aren't going to go out of their way to write a 5-page dissertation about how generics would help solve a problem they worked around, but that's not a justification for not including generics. The fact you have to write orders of magnitude more code in order to work around a lack of generics is ridiculous, and I find it frustrating every time I have to do it. Will I eventually crack and write a series of blog posts that just rant about every single fucking problem I have with Go? Maybe. But it seems quite unreasonable to only want reviews which effectively must be of the form of a coherent rant.
Comments
I use Go quite a lot, and I agree with their "irrational arguments". It seems quite dishonest to pretend that anyone who doesn't use Go because they found it too restrictive to be "wasting their time with irrational stances". It's also quite close-minded.
You're right that most Go developers aren't going to go out of their way to write a 5-page dissertation about how generics would help solve a problem they worked around, but that's not a justification for not including generics. The fact you have to write orders of magnitude more code in order to work around a lack of generics is ridiculous, and I find it frustrating every time I have to do it. Will I eventually crack and write a series of blog posts that just rant about every single fucking problem I have with Go? Maybe. But it seems quite unreasonable to only want reviews which effectively must be of the form of a coherent rant.