Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #1874

R

rakyll.org

Personal blog · rakyll.orgprogrammingsystems

rakyll.org is a personal blog at rakyll.org about programming and systems. Since 2014, 40 different Hacker News readers have linked it 47 times, most often “Style guideline for Go packages”. It is still writing: the last post was on 2026-09-22, and you can follow it by feed.

Visit the blog
47mentions?
40HN people?
2014–2023first – last linked?
Links on Hacker News per year · peak 17 in 2017

Too few sampled comments (9) to say how often HN recommends it.?

Why HN links it

Jaana Dogan's Go-focused posts on generics, the goroutine scheduler, debugging with core dumps, and testing techniques. Commenters link them to explain how Go works internally and as practical references.

Summarised by Claude from a sample of 9 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

Most-linked posts?

  1. Style guideline for Go packages
    5 people · 5 mentions · first linked 2017-02-02
  2. The Go type system for newcomers
    4 people · 4 mentions · first linked 2017-12-29
  3. Go for Cloud
    4 people · 4 mentions · first linked 2020-02-12
  4. Generics facilitators in Go
    4 people · 4 mentions · first linked 2021-12-21
  5. Shardz
    3 people · 4 mentions · first linked 2021-12-03
  6. Inlined Defers
    3 people · 3 mentions · first linked 2020-01-22
  7. Go's work-stealing scheduler
    2 people · 2 mentions · first linked 2017-07-18
  8. Interface pollution in Go
    2 people · 2 mentions · first linked 2018-01-01
  9. Custom pprof profiles
    2 people · 2 mentions · first linked 2017-07-10
  10. The future of latency profiling in Go
    2 people · 2 mentions · first linked 2017-07-23

What Hacker News says?

  1. Go does accept pull requests, just not GitHub ones: https://golang.org/doc/contribute.html#Code_review (I don't disagree with the premise though, Go does seem to be less community-driven than Rust; e.g. Rust has 3 mozilla employees in the top 10 contributors for the most recent release[0], where as Go has 9 Googlers in its top 10[1].) [0]: https://github.com/rust-lang/rust/graphs/contributors?from=2... [1]: https://…

    Comment linking /go18cls/

    on “Rust vs. Go”
  2. Submitted Go's work-stealing scheduler as a story · 200 points

    HN discussion
  3. You can certainly use generic parameters in methods—the [T any] just has to be on SomeNonGenericType, even if it's not used inside the type itself https://rakyll.org/generics-facilititators

    Comment linking /generics-facilititators

    on “Go generics are not bad”
  4. Submitted Generics facilitators in Go as a story · 192 points

    HN discussion
  5. I believe they're talking about the semi-duck typing used in go for interfaces but I'm not certain. Interfaces are implicitly implemented with a runtime check determining whether a type x assigned to interface y is valid.This is why you'll often see an empty declaration in packages for structs intended to implement an interface like so: var _ y = x {} // syntax might be slightly wrong After writing this, I found the…

    Comment linking /typesystem/

    on “Generics facilitators in Go”
  6. Submitted The future of latency profiling in Go as a story · 145 points

    HN discussion
  7. There's a problem lurking behind this "simple" model: the goroutine you park on that blocking IO operation can't be collected reliably itself. I care about collecting goroutines, and would advocate that everyone should care about this. There's been a litany [1] of blogs about this recently, if anyone doesn't consider this self-evident. It's just systematically sane . Letting goroutines spin off into the distance wit…

    Comment linking /leakingctx/

    on “Goroutines, Nonblocking I/O, and Memory Usage”
  8. Submitted Shardz as a story · 62 points

    HN discussion
  9. A good presentation did the rounds a while ago[0] that does a deeper dive but the main things for us are the performance, smaller binaries and the improvements in tooling. The one thing I wish they added though? `go new` and have it initialise a new project structure that stopped tiny package syndrome and bizarre Makefiles in repos! [1] [0] https://docs.google.com/presentation/d/1veyF0y6Ynr6AFzd9gXi4... [1] https://…

    Comment linking /style-packages/

    on “What's Coming in Go 1.15”
  10. Submitted Go for Cloud as a story · 5 points

    HN discussion
  11. Cross posting my comment from the crusty news aggregator site: I liked this blog post and agree with most of it. But I think its section on interfaces is a bit muddled. It links to this article[1] for more advice, and while the article sounds nice in principle from the perspective of someone publishing a library for others to use, I’ve found other techniques to be valuable as well. One technique I’m particularly fon…

    Comment linking /interface-pollution/

    on “Testing techniques in Go”
  12. Submitted Go for Cloud as a story · 4 points

    HN discussion
  13. via https://rakyll.org/generics-facilititators/ Example: https://go.dev/play/p/as3rT4fB3cn // Invocation: strings := []string {"1", "2", "3"} ints, err := Mapper[string, int](strings).MapErr(strconv.Atoi) strings = Mapper[string, string](strings).Map(func(s string) string { return s + "_suffix" }) // Definition: type Mapper[T, U any] []T func (ts Mapper[T, U]) Map(f func(T) U) (us []U) { us, _ = ts.MapErr(func(t T)…

    Comment linking /generics-facilititators/

    on “Go Developer Survey 2021 Results”
  14. Submitted Interface pollution in Go as a story · 4 points

    HN discussion
  15. Haven't tried it personally, but based on a recent article shared at r/golang ( https://rakyll.org/coredumps/ , via https://www.reddit.com/r/golang/comments/6cvtd6/debugging_go... ), delve seems to show the contents of an .s file allright.

    Comment linking /coredumps/

    on “Show HN: C to Go Assembly”
  16. Submitted The Go type system for newcomers as a story · 4 points

    HN discussion
  17. echlebek · 2018-04-30Recommends
    The way all of this works is nicely detailed here: https://rakyll.org/scheduler/

    Comment linking /scheduler/

    on “Hello Go”
  18. Submitted Golang tooling essentials: useful flags and options as a story · 4 points

    HN discussion
  19. Submitted Generics Facilitators in Go as a story · 3 points

    HN discussion
  20. Submitted Spanner's High Availability Writes as a story · 3 points

    HN discussion
  21. Submitted Go for Cloud as a story · 3 points

    HN discussion
  22. Submitted The Go type system for newcomers as a story · 3 points

    HN discussion
  23. Submitted The future of latency profiling in Go as a story · 3 points

    HN discussion
  24. Submitted Shardz as a story · 2 points

    HN discussion
  25. Submitted Few Things on Generics as a story · 2 points

    HN discussion
  26. Submitted Inlined Defers in Go 1.14 as a story · 2 points

    HN discussion
  27. Submitted Inlined Defers as a story · 2 points

    HN discussion
  28. Submitted The Golang type system for newcomers as a story · 2 points

    HN discussion
  29. Submitted Style guideline for Go packages as a story · 2 points

    HN discussion
  30. Submitted Dapper-style Stackdriver Tracing for gRPC on Go as a story · 2 points

    HN discussion

Search all of HN for rakyll.org

Linked by the same people?