Submission timeline
2007–2026One slot for every year since HN launched. Height is that year's peak points; orange marks a 100+ point or 50+ comment breakout. Select a bar to open its strongest thread.
First comments on top threads
HN comment orderThis is very nice. Does anyone have an idea of how to extend the visualization so that they could be rendered based on the actual runtime of a real program? I have a theory that much complexity could be understood if humans could just see the interactions and the data flowing. Even if the program took 100X longer to run, if you can see the bug, you can fix it. If you can see the complexity, you can understand it.
I just have to compliment the author on this, even this makes for sort of a vacuous HN comment, because it is that cool. I clicked through half-expecting "just another Go goroutine/channel tutorial", but this really is something very nice and unique, with a lot of effort put in.
The first top-level comment from each of the four biggest threads, in HN’s own order. Excerpts are shortened; open a comment for full context.
- Breakout years
- 2
- Total points
- 544
- Total comments
- 39
100+ points or 50+ comments
reference only — not used in Hall rules or ranking
reference only — not used in Hall rules or ranking
Every submission
| Date | Title as submitted | By | Points | Comments |
|---|---|---|---|---|
| 2016-01-27 | Visualizing Concurrency in GoFirst breakout | pella | 258 | 18 |
| 2017-02-10 | Visualizing Concurrency in Go | diggan | 2 | 0 |
| 2017-04-28 | Visualizing Concurrency in Go (2016)Best thread · Latest 20+ point return | velodrome | 282 | 21 |
| 2019-07-20 | Visualizing Concurrency in Go (2016) | bibyte | 2 | 0 |