Josh Haberman

Most-linked posts?

1. Parsing Protobuf at 2+GB/S: How I Learned to Love Tail Calls in C
   17 people · 30 mentions · first linked 2021-04-21
2. Parsing C++ is literally undecidable (2013)
   10 people · 10 mentions · first linked 2013-08-28
3. Hello JIT World: The Joy of Simple JITs (2012)
   8 people · 17 mentions · first linked 2013-01-01
4. LL and LR in Context: Why Parsing Tools Are Hard (2013)
   8 people · 11 mentions · first linked 2013-09-06
5. LL and LR Parsing Demystified (2013)
   6 people · 6 mentions · first linked 2013-07-22
6. LL and LR Parsing Demystified (2013)
   5 people · 5 mentions · first linked 2023-08-29
7. A tail calling interpreter for Python (already landed in CPython)
   5 people · 5 mentions · first linked 2025-02-17
8. Bloaty McBloatface: a size profiler for binaries
   4 people · 6 mentions · first linked 2016-11-07
9. /2013/08/parsing-c-is-literally-undecidable.html
   4 people · 4 mentions · first linked 2020-07-15
10. No-Panic Rust: A Nice Technique for Systems Programming
    3 people · 5 mentions · first linked 2025-02-03

What Hacker News says?

1. haberman · 2024-01-09

   The article describes that the new JIT is a "copy-and-patch JIT" (I've previously heard this called a "splat JIT"). This is a relatively simple JIT architecture where you have essentially pre-compiled blobs of machine code for each interpreter instruction that you patch immediate arguments into by copying over them. I once wrote an article about very simple JITs, and the first example in my article uses this style:…

   Comment linking /2012/12/hello-jit-world-joy-of-simple-jits.html

   on “Python 3.13 Gets a JIT”
2. signa11 · 2021-04-25

   Submitted Parsing Protobuf at 2+GB/S: How I Learned to Love Tail Calls in C as a story · 586 points

   HN discussion
3. jacobolus · 2021-05-04

   https://blog.reverberate.org/2020/05/29/hoares-rebuttal-bubb...

   Comment linking /2020/05/29/hoares-rebuttal-bubble-sorts-comeback.html

   on “Back in 1993, I was taking a number theory class”
4. fanf2 · 2024-08-19

   Submitted Parsing protobuf at 2+GB/s: how I learned to love tail calls in C (2021) as a story · 366 points

   HN discussion
5. throw0101c · 2025-10-30

   See perhaps various "What every programmer / CSist should know about floating-point arithmetic" papers and articles: * David Goldberg, 1991: https://dl.acm.org/doi/10.1145/103162.103163 * 2014, "Floating Point Demystified, Part 1": https://blog.reverberate.org/2014/09/what-every-computer-pro... ; https://news.ycombinator.com/item?id=8321940 * 2015: https://www.phys.uconn.edu/~rozman/Courses/P2200_15F/downloa...

   Comment linking /2014/09/what-every-computer-programmer-should.html

   on “987654321 / 123456789”
6. haberman · 2014-09-15

   Submitted What every computer programmer should know about floating point, part 1 as a story · 323 points

   HN discussion
7. haberman · 2022-07-13

   I wrote an article about my motivation for it: https://blog.reverberate.org/2021/04/21/musttail-efficient-i...

   Comment linking /2021/04/21/musttail-efficient-interpreters.html

   on “Tell HN: We are trying to get tail calls into the WebAssembly standard”
8. ingve · 2016-02-23

   Submitted LL and LR in Context: Why Parsing Tools Are Hard (2013) as a story · 222 points

   HN discussion
9. haberman · 2025-03-10

   I think it's important to note that a primary motivation of the tail call interpreter design is to be less vulnerable to the whims of the optimizer. From my original blog article about this technique ( https://blog.reverberate.org/2021/04/21/musttail-efficient-i... ): > Theoretically, this control flow graph paired with a profile should give the compiler all of the information it needs to generate the most optimal c…

   Comment linking /2021/04/21/musttail-efficient-interpreters.html

   on “Performance of the Python 3.14 tail-call interpreter”
10. chmaynard · 2025-02-03

    Submitted No-Panic Rust: A Nice Technique for Systems Programming as a story · 204 points

    HN discussion
11. asicsp · 2025-03-10

    Related discussions: https://docs.python.org/3.14/whatsnew/3.14.html#whatsnew314-... --> https://news.ycombinator.com/item?id=42999672 (66 points | 25 days ago | 22 comments) https://blog.reverberate.org/2025/02/10/tail-call-updates.ht... --> https://news.ycombinator.com/item?id=43076088 (124 points | 18 days ago | 92 comments)

    Comment linking /2025/02/10/tail-call-updates.html

    on “Performance of the Python 3.14 tail-call interpreter”
12. haberman · 2017-03-20

    Submitted Bloaty McBloatface: a size profiler for binaries as a story · 202 points

    HN discussion
13. haberman · 2016-11-28

    This. The AT&T syntax for x86 thing is a huge mistake. All the official docs are Intel syntax. Intel syntax is easier to read and write. Half the gotchas in this article are problems that don't exist in Intel syntax, like the instruction suffixes. The instruction suffixes get even weirder when you get to the sign extending instructions. I wrote an article about this here: http://blog.reverberate.org/2009/07/giving-u…

    Comment linking /2009/07/giving-up-on-at-style-assembler-syntax.html

    on “Learning to Read X86 Assembly Language”
14. bleakgadfly · 2016-09-21

    Submitted LL and LR Parsing Demystified (2013) as a story · 155 points

    HN discussion
15. haberman · 2021-04-25

    That is true, but there is always https://rr-project.org for easy reverse debugging if you're having trouble figuring out where you came from. If the alternative is to drop to assembly, a C-based approach seems quite easy to debug. You can just add printf() statements! Previously when I had been using assembly language or a JIT, I had to resort to techniques like this: https://blog.reverberate.org/2013/06/printf-deb…

    Comment linking /2013/06/printf-debugging-in-assembly-language.html

    on “Parsing Protobuf at 2+GB/S: How I Learned to Love Tail Calls in C”
16. todsacerdoti · 2021-12-18

    Submitted Thread Safety in C++ and Rust as a story · 147 points

    HN discussion
17. svnpenn · 2022-11-23

    https://blog.reverberate.org/2021/04/21/musttail-efficient-i...

    Comment linking /2021/04/21/musttail-efficient-interpreters.html

    on “Building the fastest Lua interpreter automatically”
18. haberman · 2020-05-30

    Submitted Hoare’s Rebuttal and Bubble Sort’s Comeback as a story · 147 points

    HN discussion
19. praptak · 2022-02-16

    In similar vein: parsing C++ is literally undecidable: https://blog.reverberate.org/2013/08/parsing-c-is-literally-... You can't even decide if a particular "*" is multiplication or a pointer dereference until you resolve templates, which is Turing-complete.

    Comment linking /2013/08/parsing-c-is-literally-undecidable.html

    on “Perl code that is syntactically correct only on Fridays”
20. phsilva · 2025-02-17

    Submitted A tail calling interpreter for Python (already landed in CPython) as a story · 124 points

    HN discussion
21. haberman · 2017-09-28

    I like the "window/offset" concept. I wrote an extended blog article with yet different visual aids: http://blog.reverberate.org/2014/09/what-every-computer-prog...

    Comment linking /2014/09/what-every-computer-programmer-should.html

    on “Floating Point Visually Explained”
22. umanwizard · 2019-10-04

    Submitted Parsing C++ is literally undecidable (2013) as a story · 111 points

    HN discussion
23. swolchok · 2024-11-02

    > C++ templates have a similar issue TIL! I went and dug up a citation: https://blog.reverberate.org/2013/08/parsing-c-is-literally-...

    Comment linking /2013/08/parsing-c-is-literally-undecidable.html

    on “Weird Lexical Syntax”
24. blopeur · 2022-01-28

    Submitted Hoare’s Rebuttal and Bubble Sort’s Comeback as a story · 103 points

    HN discussion
25. haberman · 2018-07-16

    Several people found my blog entry on this enlightening: http://blog.reverberate.org/2015/08/monads-demystified.html

    Comment linking /2015/08/monads-demystified.html

    on “Async and Await in Rust: a full proposal”
26. jeffreyrogers · 2014-04-06

    Submitted Hello JIT World: The Joy of Simple JITs (2012) as a story · 96 points

    HN discussion
27. haberman · 2012-05-10

    I struggled with a similar question for my low-level protobuf library UPB ( https://github.com/haberman/upb ). Here are some blog posts describing my dilemma about this: http://blog.reverberate.org/2009/11/porting-upb-to-c.html http://blog.reverberate.org/2009/12/torn-over-c-question.htm... I ultimately chose to stick with C, and I'm happy with my decision. When people ask me why I stuck with C, it's difficult to gi…

    Comment linking /2009/12/torn-over-c-question.html

    on “Why should I have written ZeroMQ in C, not C++”
28. swah · 2014-02-24

    Submitted On "The Future of JavaScript MVC Frameworks" as a story · 73 points

    HN discussion
29. haberman · 2014-06-26

    Exactly. The React paradigm is to never mutate the DOM directly, but instead let React mutate it. I wrote a friendly intro here: http://blog.reverberate.org/2014/02/react-demystified.html

    Comment linking /2014/02/react-demystified.html

    on “Epoch – A real-time charting library”
30. codezero · 2018-12-18

    Submitted Hello, JIT World: The Joy of Simple JITs (2012) as a story · 66 points

    HN discussion

Search all of HN for blog.reverberate.org

Linked by the same people?

• RRafe Colburnrc3.org
• PProbably Danceprobablydance.com
• Llcamtuf's old bloglcamtuf.blogspot.com
• Nneugierig.orgneugierig.org
• LLaurence Tratttratt.net
• JJohn Regehrblog.regehr.org
• Pplasmasturm.orgplasmasturm.org