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 · #9421

B

Blog on blog.gnoack.org

Personal blog · blog.gnoack.orgprogrammingsecurity

Blog on blog.gnoack.org is a personal blog at blog.gnoack.org about programming and security. Since 2018, 8 different Hacker News readers have linked it 27 times, most often “Error handling: No error left behind”. It is still writing: the last post was on 2026-10-29, and you can follow it by feed.

Visit the blog
27mentions?
8HN people?
2018–2026first – last linked?
Links on Hacker News per year · peak 6 in 2020

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

Why HN links it

HN readers link this blog for posts on reading mailing lists with the lei tool and public-inbox archives, and for a series on moving POSIX signal handling and IO into userspace, including file descriptions.

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

Most-linked posts?

  1. Error handling: No error left behind
    2 people · 3 mentions · first linked 2018-10-11
  2. Opening /proc/self/fd/1 is not the same as dup(1)
    2 people · 2 mentions · first linked 2024-02-19
  3. The empty Makefile is valid
    2 people · 2 mentions · first linked 2023-05-12

What Hacker News says?

  1. I've written an article on error handling some point and ended up with: "An error is when the program is operating outside the intended path of execution." What counts as intended is a question of definition, but in concrete examples of local reasoning within a function this question is usually easier to answer. Thinking about it in terms of (explicit or implicit) contracts, like Bertrand Meyer, sounds like a smart…

    Comment linking /post/error_handling/

    on “Programming Paradigms for Dummies: What Every Programmer Should Know (2009) [pdf]”
  2. Submitted Goroutines and APIs as a story · 106 points

    HN discussion
  3. There are tools to import mails into whichever email client you prefer, especially if the list is archived on a public-inbox instance, which is the best mailing list archiving system so far. https://lwn.net/Articles/875239/ https://blog.gnoack.org/post/lei/ https://people.kernel.org/monsieuricon/lore-lei-part-1-getti... https://b4.docs.kernel.org/ https://github.com/mikwielgus/forum-dl

    Comment linking /post/lei/

    on “Why use mailing lists?”
  4. Submitted Opening /proc/self/fd/1 is not the same as dup(1) as a story · 61 points

    HN discussion
  5. Crucially, no. “File descriptions” (or “open file descriptions”; classically, struct file[1]) are what file descriptors designate. The whole hubbub is because a file description is not just a device number, an inode number, and a set of already-checked permissions; they are all that and a position in the file, and that position gets shared along with the rest of the description when you dup(), fork(), or sendmsg() t…

    Comment linking /post/proc-fd-is-not-dup/

    on “Towards userspaceification of POSIX – part I: signal handling and IO”
  6. Submitted The Setup-Cleanup Problem as a story · 48 points

    HN discussion
  7. https://blog.gnoack.org/ Mostly Linux, Sandboxing, Go and sometimes other Unixy or programming language topics. Not posting much, but with a high signal to noise ratio.

    Comment linking /

    on “Ask HN: Could you share your personal blog here?”
  8. Submitted Google Big Sleep: Linux Vulnerabilities as a story · 4 points

    HN discussion
  9. Submitted The empty Makefile is valid as a story · 3 points

    HN discussion
  10. Submitted The empty makefile is valid as a story · 3 points

    HN discussion
  11. Submitted Why use Go-Landlock for sandboxing? as a story · 3 points

    HN discussion
  12. Submitted Error handling: No error left behind as a story · 3 points

    HN discussion
  13. Submitted Landlock Your Vibe Coding as a story · 2 points

    HN discussion
  14. Submitted LLM-generated docs are usually worthless as a story · 2 points

    HN discussion
  15. Submitted The Feasibility of Pledge() on Linux as a story · 2 points

    HN discussion
  16. Submitted Error Handling Links as a story · 2 points

    HN discussion
  17. Submitted Don't check emptyness before loops as a story · 2 points

    HN discussion
  18. Submitted How to Review Code as a story · 2 points

    HN discussion
  19. Submitted Procedurally generated trees as a story · 2 points

    HN discussion
  20. Submitted Splitting a Git Commit as a story · 1 points

    HN discussion
  21. Submitted Writing Tests in Go as a story · 1 points

    HN discussion
  22. Submitted Go-style coroutines in the FN language as a story · 1 points

    HN discussion
  23. Submitted Test Cleanup in Go 1.14 as a story · 1 points

    HN discussion
  24. Submitted Why Software Design? as a story · 1 points

    HN discussion
  25. Submitted Go: Sharing templates across multiple pages as a story · 1 points

    HN discussion
  26. Submitted Shared Base Fixture technique for unit tests as a story · 1 points

    HN discussion
  27. Submitted No error left behind as a story · 1 points

    HN discussion

Search all of HN for blog.gnoack.org