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

S

strongly-typed-thoughts blog

Personal blog · strongly-typed-thoughts.net/blogprogrammingsystems

strongly-typed-thoughts blog is a personal blog at strongly-typed-thoughts.net about programming and systems. Since 2024, 9 different Hacker News readers have linked it 11 times, most often “Zig; what I think after months of using it”. It is still writing: the last post was on 2026-04-21, and you can follow it by feed.

Visit the blog
11mentions?
9HN people?
2024–2025first – last linked?
Links on Hacker News per year · peak 9 in 2025

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

Why HN links it

HN readers link this blog for its Zig writing, especially on what comptime can and cannot do and a 2025 Zig review. Comments mostly cite the posts as sources or note layout problems.

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

Most-linked posts?

  1. Zig; what I think after months of using it
    2 people · 2 mentions · first linked 2025-02-05

What Hacker News says?

  1. > But the point is that all that is done at compile time, which is also the time when all more specialised features are checked. > ... > Again, everything is checked at compile-time. Once it compiles it will work just like generics. No. My compile-time when using a library with a comptime type in Zig is not guaranteed to work because my user experience could depend on if the library writer tested with the types (or…

    Comment linking /blog/zig-2025

    on “Things Zig comptime won't do”
  2. Submitted Zig; what I think after months of using it as a story · 197 points

    HN discussion
  3. comptime can’t outright replace many language features because it chooses different tradeoffs to get to where it wants. You get a “one thing to rule all” at the expense of less declarative use. Which I already said in my original comment. But here’s a source that I didn’t find last time: https://strongly-typed-thoughts.net/blog/zig-2025#comptime-i... Academics have thought about evaluating things at compile time (or…

    Comment linking /blog/zig-2025

    on “Things Zig comptime won't do”
  4. Submitted Vim vs. Kakoune Puzzles as a story · 12 points

    HN discussion
  5. Headers are missing IDs for URL fragments to jump to e.g. https://strongly-typed-thoughts.net/blog/zig-2025#error-hand... doesn't work

    Comment linking /blog/zig-2025

    on “Zig; what I think after months of using it”
  6. Submitted Goodbye, GitHub as a story · 5 points

    HN discussion
  7. Not everyone thinks of Zig as a "no downsides and all upsides" C-replacement. First, a lot of people will take issue with it still being in beta and it being unknown how many more years will it take to reach 1.0. There are a bunch of C-replacements, or at least viable alternative languages out there. Both old and new. With more "C-killers" likely to pop-up in the not so distant future. There are also a lot of people…

    Comment linking /blog/zig-2025

    on “F8 – an 8 bit architecture designed for C and memory efficiency [video]”
  8. Submitted Zig: What I think after one month of using it (perspective of a Rust programmer) as a story · 3 points

    HN discussion
  9. Submitted Defer and Errdefer in Rust as a story · 2 points

    HN discussion
  10. Submitted Moving away from PR/MR workflow as a story · 2 points

    HN discussion
  11. Submitted The Kakoune Philosophy as a story · 1 points

    HN discussion

Search all of HN for strongly-typed-thoughts.net