# NoiseLang: Where N = 5 is a Dirac delta > A signals-and-noise course left me writing Monte Carlo math on paper and wishing the notation itself would run. Nine years later, with an AI agent doing the heavy lifting, NoiseLang became a real Monte Carlo language that runs the same fused kernel on the GPU, on every CPU core, and on WebAssembly. [View on manualmeida.dev](https://manualmeida.dev/articles/noiselang) During [my telecommunications degree](https://www.tel.uva.es/en/studies/degrees/itec.htm) I took a course on signals and noise, I spent a lot of evenings writing probability by hand: expectations, variances, the odds of two random variables landing in some region. It always sucked, when I tried to run it on a computer, so much boilerplate. That wish became [NoiseLang](https://noiselang.com). I started it about nine years ago, however, I never finished it. Only recently, I brought it back thanks to AI tools and something far more ambitious than what I could have built alone the first time. ## Everything is a distribution The whole language hangs on one idea, that **every value is a probability distribution**. A plain number is a Dirac spike, a distribution with all its weight on a single value. Since constants and random variables are the same kind of object, every operator in the language maps distributions to distributions. Purists will tell you that the Dirac delta belongs to continuous densities and has no business on a six-sided die, and they are right. What I mean is the Dirac measure, all the weight on one point, which works fine on a die. Noise never evaluates a density anyway, it draws samples. And a constant collapses back to a plain integer in the graph, so `5` costs nothing. A name always refers to one fixed node, the same way `X` is the same `X` across a whole page of math. So `X + X` is `2X` and `X - X` is exactly `0`. If you want variable independence you write separate draws, ie, using `~` multiple times, or `~[N]` to draw `N` independent variables into a vector. ``` X ~ unif_int(1, 6) Y ~ unif_int(1, 6) X + Y # two independent dice, a real 2d6 distribution ``` Nothing runs until you ask for some results, for example, `P(X + Y < 10)`, at that moment it forces the runtime to run millions of simulations (across all cores, if available) and return an estimate with a standard error attached. ``` Bday = unif_int(1, 365) days ~[23] Bday # 23 people in a room P(has_duplicates(days)) # the birthday paradox, about 0.507 ``` This is much easier to watch than to describe, so I built some cool demos! > *[Interactive figure — view it at https://manualmeida.dev/articles/noiselang]* ## Why it sat for nine years The design was never the hard part, because a parser and a tree-walking interpreter for this language is a weekend of work. The problem was everything else, writing an efficient Monte Carlo runtime, instead of a naive interpreter, conditional bayesian inference, and more. Current version is a compiler with a GPU backend (WGSL through [wgpu](https://wgpu.rs/)), a [WASM](https://webassembly.org/) backend, and a pile of careful numerical code, so for a cute-weekend project it stayed permanently out of reach. ## Building the ambitious version with an agent At my day job and side projects, I am experimenting with the boundaries of what today's AI agents can do. For example, I am also porting a game I built 15 years ago for iOS, in archaic Objective-C to a modern game engine (with relative success). With NoiseLang, I realized, AI is great at building the JIT parts, the runtime parts, the numerical parts, but it sucks at coming up with good language design ideas, many times overriding existing language features for different purposes, or coming up with different syntax for non-orthogonal features. > *[Interactive figure — view it at https://manualmeida.dev/articles/noiselang]* ## One IR, three backends The first plan was to compile the graph into WASM and let a WASM runtime JIT it for me, because that runtime was surely going to optimize better than any compiler I could write myself. While exploring that, I realized I could reach for the JIT optimizer directly and skip the WASM step, so the first native backend was a [Cranelift](https://cranelift.dev/) JIT, a killer library for a project like this, NoiseLang ran at native speed and I barely wrote any compiler. That JIT is gone now. Keep reading, because the reason it left is my favorite part of the whole project. `~` and the distribution constructors build an append-only DAG called the RvGraph. This graph is the single source of truth, which is later converted into three different code paths: - a columnar batch interpreter that works everywhere and acts as the correctness oracle; - a WGSL emitter that fuses a whole expression into one GPU compute shader; - a WASM emitter that does the same fused kernel for the browser's CPU. ```mermaid flowchart LR src["X ~ unif(1, 6)"] --> ir["RvGraph"] ir --> interp["batch interpreter"] ir --> wgsl["WGSL emitter (GPU)"] ir --> wasm["WASM emitter"] wgsl -. fallback .-> interp wasm -. fallback .-> interp ``` One shared module defines what the graph means, so the two code generators stay thin and cannot drift apart. Anything a backend can't successfully compile falls back to the interpreter, and the results stay identical across backends and core counts. All tests run in all three code paths and compared to be bit-identical. The engine picks the path per query, the same way a SQL query planner picks an execution plan: a cost model keeps the small queries on the vectorized interpreter, fans the medium ones out across every core with a work-stealing reducer, and sends the heavy ones to the GPU as one fused compute shader. You write `P(...)`, the planner does the rest. ## Making the Monte Carlo loop cheap All the performance work is about one loop: draw a few million samples, evaluate the expression on each, and reduce the results. A handful of techniques carry most of it, while keeping the results deterministic (that was the hard part). Kernel fusion keeps every intermediate value in registers, so an arithmetic-heavy expression stays in registers. The PRNG compiles into the kernel, and the `ln`, `sin`, and `cos` become inline polynomial approximations, speeding up the kernel by a factor of 2. My favorite trick used to be in the RNG. The original generator ([xoshiro256++](https://prng.di.unimi.it/)) is a serial dependency chain, so instead of fighting that, the kernel ran four independent streams at once and let the out-of-order core overlap them. That trick is retired now, and the reason is better than the trick: the RNG became counter-based ([squares64](https://arxiv.org/abs/2004.06278)), a middle-square hash where every draw is a pure function of (seed, lane, source). No state to thread through the loop means any slice of the sample space can run on any core, or any GPU thread, and land bit-identical. And it is not a random pick (pun intended), the exact bit stream the engine consumes passed 1 TB of [PractRand](https://pracrand.sourceforge.net/) with zero anomalies. On my 14-core M4 Pro, a one-line `P(...)` sustains around 5.8 billion samples per second and scales about 9.6× from one core to all of them. Per core, the JIT kernel ran within about 1.15× of hand-written Rust compiled by LLVM, which told me the CPU codegen had hit its ceiling. The same fused loop, emitted as WASM, runs at roughly half to three-quarters of native speed inside V8. > *[Interactive figure — view it at https://manualmeida.dev/articles/noiselang]* ## The GPU ate the JIT A few weeks after I published this article, I deleted the JIT. The idea clicked when I noticed that a Monte Carlo query is already shaped like a compute shader: one pure kernel evaluated over millions of independent lanes, then a reduce to fold them down. That is exactly the GPU compute model, so the RvGraph got a WGSL lowering, and thanks to [wgpu](https://wgpu.rs/) the same emitter reaches Metal, Vulkan and DirectX 12 on native, and WebGPU in the browser. One GPU backend to maintain, instead of one per platform. Then I measured the full example corpus on the M4 Pro: | backend | corpus total | speedup | | ------------- | ------------ | --------- | | interpreter | 3854 ms | 1.00× | | Cranelift JIT | 3274 ms | 1.18× | | GPU | 923 ms | **4.17×** | | JIT + GPU | 843 ms | 4.57× | Once the GPU exists, everything the JIT adds is 80 ms, and it only ever worked on native. So it went, 1,834 lines and four dependencies deleted, and the shipped CLI jumped from the interpreter to the GPU by default. Deleting a backend was the fastest release I ever cut! The heavy examples are where it gets fun. A quantization example that draws random rotation matrices went from 1474 ms to 55 ms (26×). The 100-prisoners simulation needed real compiler work first: by the time the emitter sees the graph, a `for` loop is unrolled into ~15,000 data-dependent reads, and the Metal shader compiler takes 2.2 seconds to chew on that. The fix was to capture the loop as a single node at eval time and emit it back as an actual WGSL loop, and the simulation dropped from 59 ms to 2.8 ms. ## Where Noise sits NoiseLang is a toy language, **you probably should not use it for anything serious**, however I wish this language existed during my university days. For a language nerd, it's a small expression-based language over a static random-variable algebra, with forward Monte Carlo and rejection-based conditioning. You might ask, how does it compare to NumPy or Stan? NumPy makes you write the simulation yourself, and Stan makes you declare a model and wait for a sampler. Noise lets you write the probability as math while running Monte Carlo under the hood to get the answer. > *[Interactive figure — view it at https://manualmeida.dev/articles/noiselang]* Stan and PyMC beat Noise at the thing they're built for, fitting a posterior to lots of continuous data with their HMC/NUTS samplers, and NumPy beats it at raw array crunching. Conditioning in Noise is rejection-based, so it works great for a handful of discrete observations but becomes useless for ten thousand continuous measurements, and there is no stateful simulation yet (no Markov chains yet). Noise wins when you have a probability question and you wanna know the answer without much hassle. So use Noise for the whiteboard stage of a problem, when you want to run the math you just wrote, and move to Stan or PyMC when you need a real posterior, or to NumPy and JAX when you need to go to production. ## Back to signals and noise Going back to my university days, there was this subject called "Señales Aleatorias Y Ruido", which is a spanish translation of "Random Signals and Noise".
Cover of the textbook Señales Aleatorias y Ruido
The textbook, in all its glory.
This subject was the nightmare of many students, including myself, in fact, I failed it. Truth be told, I didn't put enough effort into it during the first year, but it changed when I had the take the same subject again in the second year. The professor was great, and made the subject interesting. The things that blew my mind was how he could model why FM survives a noisy channel when AM doesn't. So, here is my tribute to the subject, a one-screen Noise program that models why FM survives a noisy channel when AM doesn't. > *[Interactive figure — view it at https://manualmeida.dev/articles/noiselang]* One caveat, and `roger_` on Hacker News caught it before I did. The program above modulates phase, not frequency, so technically it is PM. For the single tone I am sending, PM and FM are the same thing up to a scale factor and a shift, so the demo still shows what I want it to show, but real FM would differentiate the message before it goes into the phase. Now I want to write that version, because FM should pull even further ahead once the message stops being a single tone. ## Run NoiseLang in the browser Everything above runs on [`@noiselang/core`](https://www.npmjs.com/package/@noiselang/core), thanks to the Rust engine compiled to WebAssembly. ```bash npm install @noiselang/core ``` ```ts const result = await run(` X ~ rand::unif(-1, 1); Y ~ rand::unif(-1, 1); 4 * P(X^2 + Y^2 < 1) `); console.log(result.value); // "3.1415…" — the last statement's value console.log(result.output); // everything Print(...) emitted ``` `run` never throws, failures come back on `result.error` with a source span. There is also `runWithIntrospection`, the API behind the variable inspector at [noiselang.com](https://noiselang.com). And when the page has WebGPU available, the heavy queries run on your GPU with the same WGSL shaders as native. Everything else stays on the WASM kernel, so nothing breaks on browsers that don't have it. NoiseLang is playable in the browser at [noiselang.com](https://noiselang.com). Open it, type `X ~ unif(-1, 1); Y ~ unif(-1, 1); 4 * P(X^2 + Y^2 < 1)`, and watch a few million draws estimate π from your browser tab. ## Appendix: prior art I posted this on [Hacker News](https://news.ycombinator.com/item?id=48803791) and the thread turned into a reading list, which is the best thing that can happen to you when you ship a toy language. NoiseLang is not the first language to treat probability as a first-class value, not even close, so here is what people pointed me to: - [monad-bayes](https://monad-bayes.netlify.app/), a Haskell library where the same "everything is a distribution" idea falls out of the monad, courtesy of `bradrn`. I had no idea Haskell could express this so directly. - [webppl](https://docs.webppl.org/), [Anglican](https://probprog.github.io/anglican/), [Stan](https://mc-stan.org) and [PyMC](https://www.pymc.io/), the real probabilistic programming languages, suggested by `chrisra`. If you have an actual model to fit, go there, not here. - [diceplots.com](https://diceplots.com) by `qdotme`, which keeps the distributions exactly analytical at every step and never samples. The opposite trade-off to mine, and a fun one. - ["General Purpose Convolution Algorithm in S4-Classes by means of FFT"](https://arxiv.org/pdf/1006.0764) by Ruckdeschel and Kohl, sent by `data-ottawa`. It is the paper behind the R package `distr`, and it overloads `+`, `-`, `*`, `/` on distributions by computing the convolutions with an FFT instead of sampling them. Exactly the operator algebra I wanted, arrived at from the other direction. - `kccqzy`'s [work on probabilistic program inference](https://github.com/kccqzy/probabilistic-program-inference), which handles loops without Monte Carlo at all. He also asked the question I was hoping nobody would ask, which is how NoiseLang handles loops, and the answer is that it does not. Big thanks also to `RossBencina` and `thrtythreeforty`, who pushed on the RNG trick until I understood my own benchmark better, and to `roger_`, who noticed that my FM demo is really doing phase modulation. This is why you post your toys! --- ## About the author Manuel Martínez-Almeida (Manu) is a principal engineer at Builder.io, where he sets the technical direction for the AI agent platform across product, design, and code. He is the creator of Gin (the Go web framework with ~88k GitHub stars and 290k+ dependent projects), helped take Qwik from proof-of-concept to production including its Rust compiler and resumability model, and designed the compiler architecture and virtual DOM for Stencil. His work sits where performance, systems, and developer experience meet — compilers, language runtimes, web frameworks, GPU rendering, and distributed infrastructure serving billions of requests a day. He is based between Lisbon and Budapest. - **Name:** Manuel Martínez-Almeida (Manu) - **Role:** Principal Engineer at Builder.io - **Focus:** compilers, language runtimes, web frameworks, GPU rendering, distributed infrastructure, developer experience, AI agents, open source - **About:** https://manualmeida.dev/articles/about/ - **GitHub:** https://github.com/manucorporat - **Twitter/X:** https://x.com/manucorporat - **dev.to:** https://dev.to/manucorporat - **Website:** https://manualmeida.dev