Top all-time · #6662
Max Bolingbroke
Personal blog · blog.omega-prime.co.ukprogrammingeconomics
Max Bolingbroke writes :: (Bloggable a) => a -> IO (), a personal blog at blog.omega-prime.co.uk about programming and economics. Since 2011, 12 different Hacker News readers have linked it 12 times, most often “Datastructures for External Memory (2016)”. It is still writing: the last post was on 2025-04-11, and you can follow it by feed.
Too few sampled comments (4) to say how often HN recommends it.?
Why HN links it
HN readers link this blog to clear up confusion between asynchronous and non-blocking I/O. Other links cite its posts on GHC language extensions, a C++ FizzBuzz via compiler errors, and LLVM code generation for Haskell.
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.
A programming and finance blog by Max Bolingbroke.
Most-linked posts?
- Datastructures for External Memory (2016)2 people · 2 mentions · first linked 2019-09-30
- GHC-specific Alias Analysis for LLVM2 people · 2 mentions · first linked 2011-09-30
What Hacker News says?
Note that what you're referring to as "readiness-based I/O" is not asynchronous I/O in the strictiest sense--it's actually non-blocking, synchronous I/O. I find this article helpful in clearing up confusion of asynchronous vs non-blocking I/O: http://blog.omega-prime.co.uk/?p=155
Comment linking /?p=155
on “Debugging memory corruption: who the hell writes “2” into my stack? (2016)”Submitted Datastructures for external memory as a story · 98 points
HN discussionRelease notes here: http://www.haskell.org/ghc/docs/7.4.1/html/users_guide/relea... Some good stuff in this release --- preliminary ARM support is exciting for obvious reasons, and the new kinds flags are fun if you like that sort of thing (see http://blog.omega-prime.co.uk/?p=127 for some examples)
Comment linking /?p=127
on “Haskell Platform 2012.2.0.0 released - includes GHC 7.4.1”Submitted java.nio.file.WatchService is subtly broken on Linux as a story · 85 points
HN discussionAwful and awesome at the same time. It reminds me quite a bit of FizzBuzz implemented in Haskell's type system ( http://blog.omega-prime.co.uk/?p=28 ).
Comment linking /?p=28
on “Solving FizzBuzz with C++ compiler error messages”Submitted The Business of the AI Labs as a story · 19 points
HN discussionMy understanding is that the main problem is translating from Haskell to LLVM IR is a lossy process, not the difference between LLVM 2.8 and LLVM 3.4. This blog post demonstrates one such issue: http://blog.omega-prime.co.uk/?p=135 Quote: "In particular, LLVM conservatively assumes that GHC's stack and the heap may alias". LLVM has to assume that short of Haskell-specific analysis, so updating to LLVM 3.4 won't help…
Comment linking /?p=135
on “Optimising Haskell for a tight inner loop”Submitted Everything You Never Wanted To Know About DLLs as a story · 4 points
HN discussionSubmitted Datastructures for External Memory (2016) as a story · 3 points
HN discussionSubmitted Security implications of PEP383 as a story · 2 points
HN discussionSubmitted Datastructures for External Memory as a story · 1 points
HN discussionSubmitted GHC-specific Alias Analysis for LLVM as a story · 1 points
HN discussion