Ivan Daniluk
divan.dev · Personal blog · on HN since 2019
Ivan Daniluk, a Go developer, writes about concurrency visualization, visual programming, fountain codes, and his experience with Go and EdgeDB.
What HN saysHN commenters praise his 'Visualizing Concurrency in Go' post as their favorite visualization of concurrency and like his animated analogies.
17HN people shared it
9linked it in comments
10stories submitted
473story points
3 months agolast shared
2019people per year2026
Most-shared posts
- 1Visualizing Concurrency in Go (2016)5 people · 3 points · first shared 2019 · discussion on HN
- 2Rethinking Visual Programming with Go4 people · 438 points · first shared 2019 · 78 comments on HN
- 3Data transfer with animated QR codes (2019?)3 people · 20 points · first shared 2021 · discussion on HN
- 4One Year with EdgeDB3 people · 8 points · first shared 2022 · discussion on HN
- 5Fountaincodes3 people · first shared 2023
- 6I Still ️Love You, Gopath1 people · 2 points · first shared 2019 · discussion on HN
- 7How to Complain about Go1 people · 2 points · first shared 2020 · discussion on HN
- 8Homepage1 people · first shared 2023
- 9Flutter go1 people · first shared 2022
- 10Torch.gif1 people · first shared 2021
- 11NoSystem.pdf1 people · first shared 2022
What HN people wrote when they linked it
TechBro8615 · 2023-04-26
Not that it would apply in this particular case, but my all-time favorite visualization of concurrency is this 2016 blog post called "Visualizing Concurrency in Go" [0]. So good.
[0] https://divan.dev/posts/go_concurrency_visualize/
patterns · 2021-07-02
Oh, this is great. I especially like the fire torch analogy and the animation you came up with (https://divan.dev/images/torch.gif).
That's exactly how I feel when reading code. Recently, I explained the problem to a dear colleague when working on a code base (with about 600K lines of code). I compared the situation to working in a large office building with all lights turned off and you have to skim through thousands of documents with a flashlight.
It's comforting to know that other people feel the same way.
divan · 2021-07-01
Great job on summarizing and categorizing tons of opinions in one post!
Shameless plug of my take on rethinking visual programming couple of years ago: https://divan.dev/posts/visual_programming_go/
shabbyrobe · 2019-06-05
The author of this post is also the author of the fantastic "Visualizing Concurrency in Go" [1] article.
[1]: https://divan.dev/posts/go_concurrency_visualize/
legulere · 2026-08-06
The actual article explaining the use for fountain codes in this use case:
https://divan.dev/posts/fountaincodes/
pveierland · 2023-02-20
Nice! It's such a neat way to transfer information :)
This guy extended the idea using fountain codes, which allows you to miss arbitrary frames and still recover the full message without waiting for the missed frames to re-appear:
https://divan.dev/posts/fountaincodes/
1st1 · 2022-07-28
The Go client implements the full client API, but yeah, it lacks the query building capability. We want all of our client APIs to have it; it's a matter of time, but I don't have a concrete ETA on when we get to it. Hopefully in the coming months. Here's a blog post by one of our users and it has some feedback on edgedb-go: https://divan.dev/posts/edgedb/
dtonon · 2021-09-11
Maybe this could interest: https://divan.dev/posts/animatedqr/
breck · 2019-06-14
Cool! I've worked in this space for years as well. Another good recent article about visual programming is: https://divan.dev/posts/visual_programming_go/