Fil's Unbelievable Garbage Collector
fil-c.org
What Is the Fourier Transform?
quantamagazine.org
Stripe Launches L1 Blockchain: Tempo
tempo.xyz
Escaping the odds and a formula for life (2024)
farhadg.com
Rasterizer: A GPU-accelerated 2D vector graphics engine in ~4k LOC
github.com
io_uring is faster than mmap
bitflux.ai
Evolving the OCaml Programming Language (2025) [pdf]
kcsrk.info
Wikipedia survives while the rest of the internet breaks
theverge.com
WiFi signals can measure heart rate
news.ucsc.edu
Forking Chrome to render in a terminal (2023)
fathy.fr
Atlassian is acquiring The Browser Company
cnbc.com
Classic 8×8-pixel B&W Mac patterns
pauladamsmith.com
Building Supabase-Like OAuth Authentication for MCP Servers
hyprmcp.com
What If OpenDocument Used SQLite?
sqlite.org
How to Build a High-Performance UR5 Inverse Kinematics Solver with IK-Geo
alexanderelias.com
Show HN: Wormhole for Perplexity Comet
blog.gingerbeardman.com
Type-safe and user-friendly error handling in Swift 6
theswiftdev.com
Experimental Hook-and-Loop Attachment System for Walls and Floors
core77.com
A high schooler writes about AI tools in the classroom
theatlantic.com
Almost anything you give sustained attention to will begin to loop on itself
henrikkarlsson.xyz
I am the author of the talk here o/.
This talk is a _subjective_ take on how the OCaml programming language evolves, based on my observations over the last 10 years I've been involved with it. My aim/hope is to demystify the compiler development process and the tradeoffs involved and encourage more developers to take a shot at contributing to the OCaml compiler.
Happy to answer questions, but also, more importantly, hear your comments and criticisms around the compiler development process, ideas to make it more approachable, etc.