I don't think the examples you've provided here are indicative of a generally dismissive attitude. There's more nuance than you realize. > Sarcasm for users wh

I don't think the examples you've provided here are indicative of a generally dismissive attitude. There's more nuance than you realize. > Sarcasm for users who need to run on older linux kernels and distros The person Russ is sarcastically replying to is someone we know; a contributor to the project. I can see how it might look a bit blunt from the outside. Perhaps more illuminating is Russ' later comment on the issue: "Old operating systems will always be with us. The fact that in 2020 people will be running a Linux distribution that forked the kernel 13 years earlier does not mean we have to support it." Which I feel is entirely reasonable. > Solutions for 32bit memory leak is: works for me on 64bit We've acknowledged the issue and work is in progress to fix it. In the meantime, however, "It works on 64-bit" is a legitimate response because it's true, and there is nothing you could do to help the programs that were affected on 32-bit systems. We never closed the issue was "works for me," we just said that's a reasonable workaround for some people. The Go developers and wider community care a great deal about our users. We have some of the fastest bug fix turnaround of any project I've seen. We do, however, have our goals and priorities and sometimes people don't agree with them. There's not a lot you can do about that.