Top all-time · #11116
Burak Emir
Personal blog · burakemir.ch/postprogrammingsystems
Burak Emir's personal blog at burakemir.ch covers programming and systems. Since 2023, 7 different Hacker News readers have linked it 14 times, most often “Programming Language Semantics and Memory Safety”. It is still writing: the last post was on 2026-08-21, and you can follow it by feed.
Most-linked posts?
- Programming Language Semantics and Memory Safety3 people · 3 mentions · first linked 2026-08-21
- Indexed Reverse Polish Notation, an Alternative to AST2 people · 2 mentions · first linked 2025-12-12
- CEK and Control Operators2 people · 2 mentions · first linked 2024-01-05
What Hacker News says?
There is an old definition of language safety which means "no untrapped execution errors". It is not the only way to define safety, but it is a good way that you can adapt to various kinds of x-safety, such as memory safety. I have a little post that explains this using a few more words, if interested: https://burakemir.ch/post/memory-safety-the-missing-def/
Comment linking /post/memory-safety-the-missing-def/
on “Safe C++ proposal is not being continued”Submitted Indexed Reverse Polish Notation, an Alternative to AST as a story · 9 points
HN discussionIt is nice to see CBPV on HN. It is a calculus that deal with a fundamental choice in PL of how to approach evaluation. For a different take, here is the first part of a mini series of posts on CBPV that aims at working out the connection to logic ("polarised natural deduction"): https://burakemir.ch/post/cbpv-pt1-small-steps/
Comment linking /post/cbpv-pt1-small-steps/
on “I'm Betting on Call-by-Push-Value”Submitted Programming Language Semantics and Memory Safety as a story · 4 points
HN discussionThis is a good article. Small nit: As someone curious about a definition of memory safety, I had come across Michael Hicks' post. He does not use the list of errors as definition, and argues that such a definition is lacking rigor and he is right. He says; > Ideally, the fact that these errors are ruled out by memory safety is a consequence of its definition, rather than the substance of it. What is the idea that un…
Comment linking /post/memory-safety-the-missing-def/
on “Memory Safety for Skeptics”Submitted CEK and Control Operators as a story · 3 points
HN discussionGreat paper, thanks for sharing! The connection between programming language technology and formal logic, like here for sequent calculus, is one of the most fascinating things. For anyone who struggles with the references to \lambda-\mu-\tilde{\mu}, the notion that a continuation takes multiple arguments and that "control effects arise naturally", it may be helpful to review the CEK machine first: https://burakemir.…
Comment linking /post/cek-and-control/
on “Sequent Calculus as a Compiler Intermediate Language (2016) [pdf]”Submitted Programming Language Semantics and Memory Safety as a story · 2 points
HN discussionSubmitted Programming Language Semantics and Memory Safety as a story · 2 points
HN discussionSubmitted Building a WASM Runner with Cloud Hypervisor as a story · 2 points
HN discussionSubmitted Burak's Mangle Talk for RelationalAI as a story · 2 points
HN discussionSubmitted From Operations to Effects: A Journey Through M-Sets as a story · 1 points
HN discussionSubmitted Indexed reverse polish notation, an alternative to AST as a story · 1 points
HN discussionSubmitted Three Meanings of Effects as a story · 1 points
HN discussion