Hacker News Reader

I love the way the Go team operates, including the way the point releases are handled. The last thing this the world needs is more marketing bullshit- No nonsense, just like Go: Go by engineers for engineers. Go will do fine "marketing" itself on its merits and the merits of things created with it.

>The Go team is plugging along. Go is getting more dependable than ever. Here's what we're doing with Go, by the way. Here's the latest projects. Here's the latest tools.

gag

You realize golang.org isn't a startup right? :)-

If this is what you are looking for check this out: http://www.golangweekly.com/archive/ (or if you want smaller bites the mailing list https://groups.google.com/forum/#!forum/golang-nuts)

>don't just say the changes since 1.2, tell us everything in your ecosystem that's changed.

This is a tiny maintenance change, I don't want to read a fricking newsletter. Of course maybe I'm wrong- maybe- CVEs, and issues filed need more marketing speak too! After all, they might get linked on Hacker News! What an opportunity!

+1 to short and sweet incremental change lists. VLC / Firefox used to be this way until /someone/ deemed those not worthy. You can still get to the VLC changes which ware way more satisfying to read:

http://www.videolan.org/developers/vlc/NEWS

My goal with the mailing list post and the submission was to let as many Go users as possible that a new release is out and they should upgrade. Should I use a minor release announcement as an occasion to get people more excited about Go? I'm not sure. I like the short and sweet nature of these point releases, and I'm wary of turning them into a marketing exercise.

Otherwise, I do spend a lot of time telling people what's going on with Go. For instance, my presentation on what's new in Go 1.3 was at the top of HN for a day.

Appreciate the feedback, though.

So how is this different from any other spammer? You're get paid to use Hacker News as a Go mouthpiece to promote your product every chance you can take.

The reason why you, a Google employee working on Go, shouldn't be submitting these stories is because you have a clear conflict of interest. You think that 5 changes totaling a few dozen lines of code is worth everybody's attention because you're in the thick of it.

But really, a story like this being front page I think calls into question whether there is a voting ring or voting bot; I can't imagine more than a person or two actually looked at the changes and said this is important.

No need to be so cynical. You may not be interested in Go, but many programmers are, and many of them read HN (and vote). You underestimate the size and enthusiasm of the Go community.

Right, so please add some summary of changes/content to this. I don't have time to go through SVN commit logs, but I'm interested in Go and use it in some side projects. I want to quickly be able to say, "What changed? Can I apply it to my projects?" Not having that is wildly frustrating when I see these "version releases" where I have no clue what's worth my time.

As someone interested in Go, I looked at it because it was worth a look...

I don't expect every HN post to be "important" as that differs from reader to reader. The fact that this ended up on the front page, and doesn't contain much easily consumable information for anyone not interested in Go, should possibly tempt you to have a look at the language, instead of assuming voting rings or bots.

I personally have minimal interest in many topics that get covered on HN. I usually just don't click on them, but if they get enough coverage I'll usually check the topic out to see if my preconceptions were flawed.

See there you go. There's absolutely nothing in these 5 bug fixes of note, but I should be tempted to have a look at the language because of them? This story is just a shameless hackvertisement for Go.

> instead of assuming voting rings or bots.

I've several times in the past seen new stories critical of Go on reddit go from 1 to -20 in less than a minute. This stopped about when uriel died so I just assumed it was him, but maybe it's still going on HN. How do you explain this post being on the front page?

I explain it being it on the front page due to lots of people being interested in Go.

The same way I explain posts related to startups, open source, patent law, Bitcoin (MtGox being the current star), the NSA etc.

People are interested in different things, and HN is full of an incredibly disparate range of people. No need to assume foul play for this story, unless you'd also like to assume the same for the other categories listed above.

So in other words you are saying that people here will vote up any story about Go regardless of merit; seeing "Go" in the title makes it interesting to them.

What is it about this story of a point release with five inconsequential bug fixes that is at all interesting?

You may as well ask what's interesting about the latest IOS point release, what's interesting about the latest nginx release, what's interesting about the latest Haskell / Erlang / Dart / Oberon / Clojure release.

As I said previously, people are interested in different things. I don't see the point in expending emotion and energy getting angry about the fact that a couple of lines of text on an ephemeral web-site weren't the couple of lines of text you would have preferred to see... Do you get equally offended when the HTTP spec is discussed on HN? Or when you hear of new Kickstarter campaign on HN? or hundreds of other sub-topics which people happen to be interested in.

My reason for checking out the release notes was to see if there were any security issues that may have effected my code, and to see if there were any updates on new features etc. And no, I didn't up-vote the story at all, I just read it.

>> You may as well ask what's interesting about the latest IOS point release, what's interesting about the latest nginx release, what's interesting about the latest Haskell / Erlang / Dart / Oberon / Clojure release.

Yes, exactly so! You should ask that question. That's the question I'm asking, and not getting an answer to. The latest iOS release fixed a massive security flaw in TLS/SSL.

This Go release? According to the guy who released it, contains minor bug fixes they had been sitting on for 3 months and decided to make a point release just because it had been a while. A total non-story.

>> I don't see the point in expending emotion and energy getting angry

The name I chose is "bsdetector" and you're asking me why I would get upset at bullshit such as this Go story.

People submit their own work to HN all the time. We encourage it.

For what it's worth, I'm happy to see the Go update announcement here. I only hack occasionally on Go so I haven't updated it in a while, but seeing this post has prompted me to download the latest version.

Anecdote: I have a general interest in the progress of Go, even though I don't program in it. I clicked through, saw no real content, and moved on to the comments to see if they would talk about what changed. I'm not going to try to parse svn commits - such things are written for people who know the code.

These updates are a fantastic opportunity to talk about interesting technical points. What changed and why? You don't need to think about it as marketing, just an excuse for some quick-n-dirty tech talk.

If you teach them to long for the immensity of the sea, as it were, won't they get frustrated by building the boat and start to take dangerous short cuts so they can get out to sea, or maybe even ride whales and drown? It may also serve the purpose of marketing to keep things boring.

"plugging away" sounds scary by the way. It could imply they are thoughtless.