Live data from Hacker News

Viewing profile — _vvhw

_vvhw

HN member
Joined
Sun, Aug 17, 2025, 9:27 PM UTC
HN karma
1
Public activity
392 items

About _vvhw

No profile information was provided.

Recent public activity

  1. comment
    Comment #33340732

    Joran from TigerBeetle here! Awesome to hear that you're excited about Zig. Thanks for sharing the link to our repo also—would love to take you on a 1-on-1 tour of the codebase som…

  2. comment
    Comment #33340684

    Anecdotally again, but I've been coding in Zig since 2020 and have hit I think 2-3 compiler bugs in all that time? The first was fixed within 24 hours, in fact just before I report…

  3. story
  4. comment
  5. comment
    Comment #33203726

    Yes, we're planning also to add a kill switch to the allocator that we switch on if anything allocates after init().

  6. comment
    Comment #33196052

    Ah, missed that, thanks! I've updated the comment.

  7. comment
    Comment #33196020

    We're aware of this, in fact, and do have a plan to address virtual memory. To be fair, it's really the kernel being dynamic here, not TigerBeetle.

  8. comment
    Comment #33195968

    Static allocation has also made TigerBeetle's code cleaner, by eliminating branching at call sites where before a message might not always have been available. With static allocati…

  9. comment
    Comment #33195909

    Joran from the TigerBeetle team here. The limit of 70 lines is actually a slight increase beyond the 60 line limit imposed by NASA's Power of Ten Rules for Safety Critical Software…

  10. comment
    Comment #33195838

    It's defense-in-depth. We use what we have available, according to the context: checksums, assertions, hash chains. You can't always use every technique. But anything that can poss…

  11. comment
    Comment #33194934

    Sure! Here's an overview with references to the simulator source, and links to resources from FoundationDB and Dropbox: https://github.com/tigerbeetledb/tigerbeetle/blob/main/docs/…

  12. comment
    Comment #33194895

    Thanks! Joran from the TigerBeetle team here. Appreciate your balanced comment. To be fair, we're certainly concerned about logic errors and buffer bleeds. The philosophy in TigerB…

  13. comment
    Comment #33194710

    Joran from the TigerBeetle team here! We have a secret plan for this too. ;)

  14. comment
    Comment #33194639

    Good to be back—Joran from the TigerBeetle team here! Static allocation does make for some extremely hard guarantees on p100 latency. For example, for a batch of 8191 queries, the …

  15. comment
    Comment #33194557

    Thanks! Data Oriented Design runs like a river through TigerBeetle—it's always on our mind. By the way, have you seen Andrew Kelley's Handmade Seattle talk on Practical DOD? [1] [1…

  16. comment
    Comment #33194513

    Thanks! Joran from the TigerBeetle team here. > I would imagine this would be potentially more efficient than having conventional mallocs. Yes, in our experience, static allocation…

  17. comment
    Comment #33194455

    Thanks! Joran from the TigerBeetle team here. TigerBeetle's storage engine is designed also for range queries, and we have some interesting ideas for our query engine in the works.…

  18. comment
    Comment #33194379

    Joran from the TigerBeetle team here! TigerBeetle uses Deterministic Simulation Testing to test and keep testing these paths. Fuzzing and static allocation are force multipliers wh…

  19. comment
    Comment #33194335

    Thanks! Joran from the TigerBeetle team here. This was in fact one of our motivations for static allocation—thinking about how best to handle overload from the network, while remai…

  20. comment
    Comment #32807179

    Basically, and we're huge fans of FoundationDB! As you zoom in, you will see differences. For example, TigerBeetle's data structures are all cache line aligned, and we use static a…

  21. comment
    Comment #32807175

    Thanks, it's a pleasure! Yes, with packed structs it's important to keep things carefully aligned. Have you seen this post [1] about struct packing? This is what we did for TB's st…

  22. comment
    Comment #32789909

    Thanks @eternalban! Awesome to read your comment here—appreciate the well wishes!

  23. comment
    Comment #32789889

    To be clear, this was out of scope of the bounty, it was a bug in Apple, that TB awarded anyway.

  24. comment
    Comment #32789344

    You could one day replace the state machine with your own and have, for example, Redis.

  25. comment
    Comment #32789337

    You're right.