Personally I enjoy reading other people's code. Sometimes it inspires me, sometimes it educates me, and sometimes it just frustrates me - though thankfully that's less common than the former two. If a Show HN was written in a language I can't program in nor have any interest in learning, then there's little point in me reading the code.
Other people will have their own reasons for caring about the language. Those reasons might not matter to you but I'm sure it matters to them.
edit: Looks like this same argument has been made plenty of times :)
Contrast with Python, Node, Ruby... apps where you have to install via Pip, NPM, Gems.
But the real answer it's that Go is in the top of the hype curve right now (I say this as a Go fan myself).
You could use Cython to create a static binary for a program written in Python.
> But the real answer it's that Go is in the top of the hype curve right now (I say this as a Go fan myself).
Hype is irrelevant to the advantages of using Go. End users of Go programs benefit for technical reasons, not social ones.
I see developer benefit if they enjoy the language, but what are the benefits to the end user?
This should apply to EVERY PROGRAM for a final user. It can be written in C, Go, Rust, PHP, compiled Ruby. Final user doesn't care what language it's written in, it shouldn't crash, should be intuitive and fast, and this can be achieved with any programming language, unless it's written in JS in Node and wrapped with Chrome, then will be lagging. Completely invalid argument for me.
This is the real winner here
That represents a large percentage, if not the overwhelming majority of users of HN. I'm surprised this question still comes up. It's a bit like when people ask on /r/gamedev showcases "why should I care what engine your game is built in?".
If you are a developer, you might want to know if you can easily make local changes, you might be interested in contributing, or you might just be interested in seeing how the internals work.
Not programming language decides it, but license application is on.
Maybe its just a fun new way to read HN, at first, but later you think ("mm.. wish it had blah feature"), and .. being a super-shart Go developer, you remember 'ah, its in Go, I can fix this..'
I generally do not objectively refuse to use something solely based on the technology behind it, but it is an important aspect to consider in the big picture while evaluating the alternatives and the actual necessity of it.