Top all-time · #16257
How Bazaar
Personal blog · how-bazaar.blogspot.co.nzprogramming
How Bazaar is a personal blog at how-bazaar.blogspot.co.nz about programming. Since 2013, 4 different Hacker News readers have linked it 5 times, most often “Stunned by Go”. The last post was in 2016, but the archive is still widely read.
Too few sampled comments (3) to say how often HN recommends it.?
Why HN links it
HN readers link this blog for its posts on Go, such as 'Stunned by Go', which examines a type cast in Go code. The linked post is cited as an example in discussions of Go's type system.
Summarised by Claude from a sample of 3 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- Stunned by Go3 people · 4 mentions · first linked 2013-07-17
What Hacker News says?
https://github.com/golang/groupcache/blob/master/sinks.go#L5... Uh oh. The dreaded cast we see here http://how-bazaar.blogspot.co.nz/2013/07/stunned-by-go.html
Comment linking /2013/07/stunned-by-go.html
on “Groupcache: an alternative to memcached, written in Go”Submitted Stunned by Go as a story · 320 points
HN discussionI'm going to note that even if Go added some kind of parametric polymorphism at this point, it still wouldn't have the same advantages as parametric polymorphism in Haskell and related languages. In Go, you can branch on types at runtime, so in a hypothetical generic Go, you could write something which appears to only ever return its argument, but does something special if the argument is of a particular type: func<…
Comment linking /2013/07/stunned-by-go.html
on “Go by Example”Submitted Loggo - Production ready logging for Go as a story · 19 points
HN discussionThe important thing is to make sure that your 'upgrade' is semantically indistinguishable from the non-upgraded version , and to the extent that it differs, document it . There's an old blog post[^1] where someone describes code that performed this kind of "interface upgrade" in a way that broke underlying assumptions about the code. This is a horrible (and unexpected!) kind of bug. One should be really, really sure…
Comment linking /2013/07/stunned-by-go.html
on “Interface Upgrades in Go”