Pangram verdict · v3.3
We believe that this entire text is AI.
AI likelihood · overall
AIArticle text · 1,764 words · 1 segments analyzed
September 22, 2026 · 43 min read Fabrice Bellard wrote the code that carries the world's video, spins up its clouds, and speaks to its cell towers. He does not give interviews. For nearly forty years he has been in conversation with one thing only, a machine, in a quiet room, with no one else invited. This is a portrait of that conversation, assembled from everyone left standing outside the door.Digits of pi, fragments of C, and the space where the man should be.On the last night of 2009, while the rest of the planet was counting backward from ten, a desktop computer in France finished counting forward. It had been running for 131 days, one consumer machine humming the same note, hnnnnnnnnnnnn, from late summer into the dead of winter. When it stopped, it held 2.7 trillion digits of pi. A world record. The previous one had needed a supercomputer. This one was set by a PC that would not have looked out of place under a teenager's desk.The digits of pi, each one rendered as a rod whose color and height encode its value. Bellard computed nearly 2.7 trillion of them on a desktop.The man who owned that PC did not hold a press conference. He posted a short note on a website that has no logo, no photographs, and a design that looks untouched since the last century. It thanked nobody. Then, as far as anyone can tell, he went back to work.His name is Fabrice Bellard. If you have watched a video on the internet today, you have used his code. If you have spun up a virtual machine, tested an app in an emulator, or stood beneath a certain kind of cellular tower, you have used his code. A rover on Mars compressed the video of its own landing with his code. He has never sat for the kind of long, confessional interview the industry hands to men who have built one tenth of what he has built.He would not sit for this one either. Nobody expected him to.There is an old way of writing about a man who will not talk to you. You go to the people who carry his work, who fight over it, who inherited it and cannot put it down, and after a while the shape of the absent man appears in the way everything around him has been bent. You do not need to see the planet. You can see it in the paths of its moons.Bellard's moons are mailing lists and commit logs, maintainers who inherited his cathedrals and spent decades keeping the roofs on, and John Carmack, the man who wrote Doom, saying out loud what the field had been muttering for twenty-five years:"I admire Fabrice Bellard. He is almost certainly a better overall programmer than I am."That is the industry's most famous engineer conceding the crown to a man most of the industry cannot pick out of a lineup. So we went to the moons.But understand what the moons are circling. At the center there is not a personality. There is a room. Nobody has described it, but every piece of software he has ever released is the transcript of the same conversation: one man, one machine, and nobody else. The machine speaks in cycles and bytes and the flat refusal of a full floppy. He answers in code. Efficiency is not his style. It is the grammar of the conversation. Every wasted byte is a word the machine will not forgive, and every human interruption, every committee, every interviewer, is noise on the line.I. The WebsiteStart at bellard.org.You type it in and you brace for the modern web, the cookie banner, the hero image, the parallax scroll, the sans-serif reassurances about mission and vision and changing the world, and instead you get... a list. A plain list of links on a white page. Black text. Blue links. It looks like something a graduate student would have put up in 1997 and forgotten about, and in a sense that is exactly what it is, except that the graduate student never stopped.Look at the list. It is not a résumé. It is an inventory of the load-bearing walls of the twenty-first century.FFmpeg. QEMU. Tiny C Compiler. QuickJS. JSLinux. BPG. A formula for the digits of pi. A world record for pi. An LTE and 5G base station. A neural-network compressor that won a benchmark. An audio codec that squeezes a song into five and a half kilobits per second, a bandwidth that a dial-up modem of the mid-1980s could not have delivered. A REST server for running large language models on your own machine. Each link goes to a page as plain as the first. Each page describes, in flat, declarative, faintly amused prose, a piece of software that would be the crowning achievement of an ordinary career.There is no About Me. There is no photograph on the home page. There is, in fact, no usable photograph of him anywhere. The one image on Wikimedia Commons that was labeled with his name turned out, on inspection, to be a photograph of the mathematician Simon Plouffe, misfiled for more than a decade, and was quietly recategorized. The most complete fan-maintained page about him notes that there are no in-focus images of Fabrice Bellard on the internet. In the age of the selfie, the man who wrote the software that carries the world's video has arranged to be, visually, a blur. A commenter on Hacker News, in a thread about one of his releases, once ticked off the absences the modern software world considers mandatory: no libraries, no continuous integration, no issue tracker, no landing page, no dashboard. Just code, and a paragraph explaining what it does, and a tarball.It is a little thrilling and a little sickening. The same commenter put his finger on the nausea. Most of the apparatus of modern software engineering, he wrote, is "a cost that only benefits for managing collaboration between teams. The smaller the team the less stuff you need." And here is a man who has skipped all of it and simply built the thing.That austerity is the first clue. The website is the man. There is nothing on it that does not need to be there, and everything that is there works. It is what a conversation looks like when only one side of it is allowed to leave the room. You get the answers. You never hear the questions.II. The Ghost in the CodecGo to the beginning of video on the internet, which is to say December 20, 2000.On that day, a developer using the name Gérard Lantau pushed the first commits of a new project. It was a mask. In the year 2000 the world of digital video was a minefield of patents, its mathematics owned, licensed, and litigated, its codecs locked in black boxes guarded by lawyers. To write a free implementation of those codecs was to paint a target on your chest. So, one presumes, the man who did it wore a false name.The project was called FFmpeg. The "mpeg" was a nod to the standards body that governed video. The "FF" stood for fast forward. And behind Gérard Lantau, as everyone in the community would eventually learn, was a twenty-eight-year-old Frenchman named Fabrice Bellard.FFmpeg: the fast-forward wordmark that now sits, unseen, behind nearly every video on the internet.He looked at the chaos of digital media, the dozens of container formats and hundreds of codecs and the incompatible, patent-shackled, vendor-locked mess of it all, and he built a universal translator. He drew a clean line between the codec layer, libavcodec, and the format layer, libavformat, and connected them with a pipeline that could swallow almost anything and spit it out as anything else. Then he wrote the codecs. Not wrapped, not borrowed. Written. Largely from scratch, largely alone, for peak performance, in C.Picture the terms of it. A codec is a negotiation with a machine over what can be thrown away. The machine says: this frame costs this many cycles, this many bytes. He answers: not that many. And back and forth, night after night, until the machine stops objecting. There was no one else in the room. Gérard Lantau was not just a shield against lawyers. It was a door, closed.When a video is uploaded to YouTube, FFmpeg transcodes it into a dozen resolutions. When a movie streams on Netflix, when a clip loops on TikTok, when a file plays in VLC, when a broadcaster pushes a signal to a satellite, when a rover on Mars squeezes the footage of its own touchdown for the long trip home, FFmpeg is down there in the dark doing the work.NASA's Perseverance rover at the rock nicknamed Rochette, September 2021. The video of its descent and landing was compressed on board with FFmpeg. Image: NASA/JPL-Caltech/MSSS.And then he left.By 2003, Bellard had drifted away from the daily grind of FFmpeg. By 2004 the project belonged to a developer named Michael Niedermayer and a cadre of volunteers, and he had walked. This is the signature, the thing every moon describes in the same stunned tone. He builds the skyscraper alone. He hands over the keys. He does not look back.The people who inherited the keys will tell you what it is like to live inside a Bellard building. It is fast. It is brilliantly conceived. And it is, in places, nearly impossible to read. Bellard is a three-time winner of the International Obfuscated C Code Contest, and that mindset, the ability to hold an intricate architecture whole in one skull, bleeds into the serious work. The early code was so tightly wound around its own logic that untangling a piece of it often bred more bugs than it killed.The community took on the same temperament. A 2001 LinuxWorld review of the neighboring MPlayer project, whose developers soon became FFmpeg's, found them relishing "nothing more than belittling their users"; a later retrospective boiled that down to software by Marquis de Sade. In 2011 the fights over leadership went nuclear and a faction forked the project as Libav. For years there were two FFmpegs hurling code at each other, until Libav was quietly declared dead around 2020.Every word of that war was human noise. Bellard was not in it. He had left the room the moment other voices came into it. Through all of it, the original kept running. Kostya Shishkov, a former FFmpeg developer who wrote a long, sardonic history of the project, shrugs that it has reached "too big to die" status. The phrase