I really dislike how every point release of certain projects (Go and Gitlab being prime examples) gets onto the HN frontpage. Even as someone who loves some of the projects, I find it to be a problem. Yet I don't want to "flag" the post, because I assume there is some kind of penalty for the submitter, beyond mere downvoting. Maybe it makes sense to have some kind of option to indicate a story fits site guidelines, b…
I like it when there's a blog post with the release, explaining a new approach to garbage collection in Go, or a new abstraction to organize processes in Elixir, etc. But this particular post appears to be just some fixes with no context so I don't see the point...
Go 1.7.1 Released
21–30 of 30 posts
Re: Go 1.7.1 Released
#22I really dislike how every point release of certain projects (Go and Gitlab being prime examples) gets onto the HN frontpage. Even as someone who loves some of the projects, I find it to be a problem. Yet I don't want to "flag" the post, because I assume there is some kind of penalty for the submitter, beyond mere downvoting. Maybe it makes sense to have some kind of option to indicate a story fits site guidelines, b…
Re: Go 1.7.1 Released
#23I really dislike how every point release of certain projects (Go and Gitlab being prime examples) gets onto the HN frontpage. Even as someone who loves some of the projects, I find it to be a problem. Yet I don't want to "flag" the post, because I assume there is some kind of penalty for the submitter, beyond mere downvoting. Maybe it makes sense to have some kind of option to indicate a story fits site guidelines, b…
Heck, lately one can't even dislike Google's projects here. They have so many employees in the pr team here that you'll get moded down fast. Just watch my post tank now for stating this.
Re: Go 1.7.1 Released
#24Earlier quoted context omitted.
Heck, lately one can't even dislike Google's projects here. They have so many employees in the pr team here that you'll get moded down fast. Just watch my post tank now for stating this.
"Please don't bait other users by inviting them to downvote you or announce that you expect to get downvoted."
Re: Go 1.7.1 Released
#25Earlier quoted context omitted.
"Please don't bait other users by inviting them to downvote you or announce that you expect to get downvoted."
Also "Please resist commenting about being downvoted. It never does any good, and it makes boring reading" which I also disagree with. Downvoting here is sometimes worthy, but often retaliatory/punishment for world-view non-conformism, and people should be called out on it.
Re: Go 1.7.1 Released
#26I really dislike how every point release of certain projects (Go and Gitlab being prime examples) gets onto the HN frontpage. Even as someone who loves some of the projects, I find it to be a problem. Yet I don't want to "flag" the post, because I assume there is some kind of penalty for the submitter, beyond mere downvoting. Maybe it makes sense to have some kind of option to indicate a story fits site guidelines, b…
It's not like someone submitted it to the front page of HN? People voted it for it to come up here... and that itself should be reason enough.
Re: Go 1.7.1 Released
#27I really dislike how every point release of certain projects (Go and Gitlab being prime examples) gets onto the HN frontpage. Even as someone who loves some of the projects, I find it to be a problem. Yet I don't want to "flag" the post, because I assume there is some kind of penalty for the submitter, beyond mere downvoting. Maybe it makes sense to have some kind of option to indicate a story fits site guidelines, b…
Re: Go 1.7.1 Released
#28The 14 issues tagged 1.7.1: net: retry DNS lookups before failure? io: endless loop in MultiReader in Go 1.7 path/filepath: EvalSymlinks is broken for relative paths on Windows net/http/httputil: Proxy terminates HTTP/2 stream before reading response body. hash/crc32: wrong output for unaligned input on s390x cmd/compile: incorrect assignment to uint64 via pointer converted to *uint16 (new in 1.7) doc: deprecation me…
Re: Go 1.7.1 Released
#29The 14 issues tagged 1.7.1: net: retry DNS lookups before failure? io: endless loop in MultiReader in Go 1.7 path/filepath: EvalSymlinks is broken for relative paths on Windows net/http/httputil: Proxy terminates HTTP/2 stream before reading response body. hash/crc32: wrong output for unaligned input on s390x cmd/compile: incorrect assignment to uint64 via pointer converted to *uint16 (new in 1.7) doc: deprecation me…
> nil pointer dereference in closeConnIfStillIdle What happens here? Does Go suffer from boundary access issues that C has? You know, in Rust, you don't have to worry about that, but is it the same for GO?
It has NPE (like Java or C#), though in some conditions it'll behave more like Objective-C.
Re: Go 1.7.1 Released
#30I really dislike how every point release of certain projects (Go and Gitlab being prime examples) gets onto the HN frontpage. Even as someone who loves some of the projects, I find it to be a problem. Yet I don't want to "flag" the post, because I assume there is some kind of penalty for the submitter, beyond mere downvoting. Maybe it makes sense to have some kind of option to indicate a story fits site guidelines, b…