Kilian (@Kilian) profile picture

No soy Kilian Jornet (@kilianj), él corre más, pero yo llegue primero a Twitter...

Joined April 2007
Photo by Kilian (@Kilian)Photo by Kilian (@Kilian)Photo by Kilian (@Kilian)Photo by Kilian (@Kilian)Photo by Kilian (@Kilian)Photo by Kilian (@Kilian)Photo by Kilian (@Kilian)Photo by Kilian (@Kilian)Photo by Kilian (@Kilian)Photo by Kilian (@Kilian)
Kilian retweeted
7
20
4
147
2,592
Kilian retweeted
Hamilton spent years trying to build a 3D number system and failed every time. On October 16th, 1843, crossing a bridge in Dublin, he realized the answer wasn't three dimensions but four - and carved the equation into the stone on the spot. That number system now runs inside every 3D graphics engine, every robotics controller, and every LLM embedding space that maps language into high-dimensional geometry. Quaternions describe rotation more efficiently than matrices and without the numerical drift that breaks other methods. The same four-dimensional structure also describes how two-state quantum systems behave - the spin of an electron, the polarization of a photon. This video builds the full geometric intuition using stereographic projection, mapping a 4D hypersphere into the 3D space you can actually see. 27 minutes. Bookmark & watch today. The number system that powers every 3D engine and nobody taught you about.
7
134
12
871
78,507
Kilian retweeted
¿Qué significan los nombres de los pueblos y ciudades de España? En 1568, el maestre de campo Pedro de Ortega Valencia navegaba por el Pacífico con la expedición de Álvaro de Mendaña. Al avistar una isla grande y fértil le puso el nombre de su pueblo: Guadalcanal, provincia de Sevilla. Cuatro siglos después desembarcaron allí los marines. La batalla más citada del Pacífico se llama como un pueblo de la Sierra Norte sevillana de poco más de dos mil vecinos. El "guada-" es el árabe wadi, "río" o "valle". Guadalquivir es al-wadi al-kabir, "el río grande". Guadalajara, wadi al-hiyara, "río de las piedras". Alcalá es al-qal'a, "el castillo", y Alcántara, al-qantara, "el puente". Descripciones corrientes que se quedaron pegadas al lugar cuando cambió la lengua. Del segundo elemento de Guadalcanal se sigue discutiendo. Medinaceli no es "la ciudad del cielo", por mucho que lo repitan las guías. Es madinat, "ciudad de", más un nombre propio: Salim, del linaje beréber de los Banu Salim, o el viejo topónimo prerromano Ocilis. Los especialistas discuten cuál de los dos. León no viene del animal, sino de Legio. Allí acampó la Legio VI Victrix y, desde el 74 d.C., la VII Gemina. De legionem salió leonem, y de ahí León. El león del escudo llegó mucho después, cuando no se recordaba ya el origen. Santander tampoco sale de San Andrés. Sale de Sancti Emeterii, genitivo del monasterio de San Emeterio y San Celedonio: Sanct Emeter, Santemeder, Santemder, Santander. De las advocaciones dobles solía sobrevivir solo el primer santo. A Celedonio se lo comió la fonética. Zaragoza es Caesaraugusta, Pamplona es Pompaelo y Mérida es Emerita Augusta. Dos capitales llevan el nombre de un político romano, Augusto y Pompeyo. La tercera lo lleva por los soldados licenciados, los eméritos, a los que se asentó allí: básicamente fue un retiro para pensionistas. Hay además elementos que se repiten por todo el mapa: Una nava es una llanura entre montes, voz prerromana emparentada con el vasco naba: las Navas de Tolosa son los llanos de Tolosa, literalmente. Un soto es el latín saltus, el bosque de ribera. Cangas viene del apelativo asturiano canga, aunque de qué significaba exactamente (valle cerrado, paso entre peñas, algo curvo) no hay acuerdo. Otros nombres no describen el terreno sino si estatus jurídico. Una puebla era el paquete de privilegios que permitía levantar un núcleo nuevo, recogido por escrito en una carta puebla. Pola es esa misma palabra en asturleonés, y Pobra, Póvoa y Pobla lo son en gallego, portugués y catalán. La de Pola de Siero la firmó Alfonso X en 1270. Todas vienen del latín populare, "llenar de gente", que a su vez sale de populari, "devastar". Villaviciosa tampoco tiene que ver con el vicio. En castellano medieval, vicioso valía por fértil y ameno: villa fértil. Y Villanueva es el nombre más frecuente del mapa municipal español, con unos sesenta y tantos municipios según recuentos no oficiales. Tanto nombre descriptivo acabó dando problemas. De los 9.266 ayuntamientos que había en 1916, más de 1.020 compartían nombre exacto. La Real Sociedad Geográfica preparó el estudio y Alfonso XIII firmó el real decreto del 27 de junio, refrendado por el conde de Romanones. Salió en la Gaceta de Madrid el 2 de julio. El preámbulo hablaba de 573 ayuntamientos; la lista que iba detrás suma 566. El criterio fue añadir ríos, montes y accidentes del terreno, por su "carácter de perpetuidad": lo que no se mueve no obliga a rebautizar el pueblo otra vez. Así nacieron Roquetas de Mar, Buitrago de Lozoya o San Fernando de Henares. Media España basa su nombre en una descripción y el apellido que la distingue se lo puso ese decreto hace poco más de un siglo. Esto es solo la entrada. El asunto lo desarrollo entero en un artículo largo que subiré próximamente.
28
168
9
735
24,914
I get this question all the time: "If AI video is so good, why aren't AI movies everywhere?" My answer never changes: Because nobody is financing them. Yet. The technology is ready. FOUND YOU: Bad Luck Brian's European Adventures Full workflow and prompts below 👇
🤖 Made with AI
1,389
306
633
3,998
6,506,113
Kilian retweeted
Harvard, fall 2009. A thousand students in one hall, and Sandel opens by asking them to steer a trolley. Brakes gone, sixty miles an hour, five workers on the track ahead, one on the side track. Almost every hand in the room votes to turn the wheel and kill the one. Then he keeps the numbers identical and changes one detail at a time. Now you are on a bridge above the track, standing next to a very heavy man. Pushing him off stops the trolley. Same math, five lives for one. The room flips. Almost nobody pushes. Now you are a surgeon with five patients dying of five different organ failures, and one healthy person asleep in the next room. Same math again. Now the room is silent. Nothing changed except your position in the story, and your entire moral system rearranged itself. That is the lecture. He never tells them which answer is correct. Then he stops using hypotheticals and reads out a real one. 1884. The yacht Mignonette goes down in the South Atlantic, 1300 miles from the Cape. Four men in a lifeboat. Dudley the captain, Stephens the first mate, Brooks a sailor, and the cabin boy, Richard Parker, seventeen years old, an orphan, on his first long voyage. Two tins of turnips. No fresh water. The boy drinks seawater and gets sick. On the nineteenth day the captain says a prayer, tells the boy his time has come, and kills him with a penknife. The three of them live on his body for four days. On the twenty fourth day a ship appears. They were rescued, taken to Falmouth, and arrested. They did not dispute a single fact. They argued necessity. A newspaper of the time opened its report with the line "A sadder story of disaster at sea was never told." The court convicted them anyway. Death sentence, later commuted to six months. Then Sandel puts it to the room as the jury, and the same students who happily killed one man to save five start hesitating. He asks them why. Because there was no lottery. Because the boy never consented. Because he was chosen for being the weakest. Every objection they raise turns out to be a principle they did not know they held. The whole course is free. Twelve lectures, no login, no cohort, no waitlist. Harvard put it online and left it there. What it costs you is watching a thousand people discover, in real time, that their moral convictions were never a system. They were a mood that changed with the camera angle.
39
141
5
1,035
206,634
This is the most popular analog computer ever produced. And you never knew you used it. But what is it? It is the automatic transmission in a gasoline car. For more than eighty years the automatic transmission has been quietly performing continuous real-time computation using pressurized fluid instead of electricity or silicon. Vehicle speed, throttle position, and the current gear are converted into their physical analogs—fluid pressures. Those pressures are then compared, summed, and routed through a network of valves. The result is a precise decision: which gear should be engaged right now. No binary digits. No clock cycles. Just physics doing arithmetic. The heart of this analog computer is the valve body. It is a precision-machined block of aluminum containing a labyrinth of channels, spools, springs, and orifices. In pure hydraulic form it is the entire program. A governor valve generates a pressure proportional to output-shaft speed. A throttle valve (or vacuum modulator) generates a pressure proportional to engine load. These two pressures meet at shift valves. When one pressure overcomes the other by a designed margin, the shift valve moves, redirecting high-pressure fluid to a clutch or band servo and the transmission changes gear. The logic is written in the diameters of the spools, the strengths of the springs, and the sizes of the orifices. Change any of those physical dimensions and the “software” changes. This system worked with remarkable perfection. It was continuous. There was no sampling delay. As road speed rose or the driver pressed harder on the accelerator, the pressures changed smoothly and the transmission responded in real time. It was robust. Heat, vibration, and electrical noise that would cripple early digital electronics were largely irrelevant to a hydraulic circuit. It was self-powered: the same oil pump that lubricated the gears also supplied the computational fluid. And it was cheap enough, once mass production began, to put sophisticated control into every family car. The first production automatic, General Motors’ Hydra-Matic of 1940, already contained the essential analog elements. By the 1950s and 1960s the valve body had become a masterpiece of fluidic computation. Engineers could tune shift points, firmness, and part-throttle behavior simply by altering spring rates and orifice diameters. For decades this purely analog machine handled everything from city traffic to highway cruising with a smoothness digital systems still struggle to match. Then the modern car demanded more information. Engine temperature, altitude, wheel slip, and emissions constraints all needed to influence shift strategy. Adding dozens of extra hydraulic sensors and valves would have made the valve body impossibly complex. The elegant solution was hybridization. A small digital computer was given authority over a few solenoid valves. Those solenoids open or close hydraulic passages, translating binary commands into pressure changes. The original analog computer still does the heavy lifting—comparing pressures and applying force—while the digital computer supplies higher-level intelligence and adaptation. The two copper-colored solenoids visible on many modern valve bodies are the interface between the two computational worlds. The digital side can now take engine coolant temperature into account so the transmission stays in a taller gear longer when the engine is cold, improving both fuel economy and emissions. It can delay upshifts during hard acceleration or command a downshift the instant the driver demands more power. Yet the fundamental decisions still occur in the continuous domain of fluid pressure. So the next time you feel a seamless gear change, remember: you are riding with one of the most successful and widely produced analog computers in history. It has been calculating with oil for longer than most of us have been alive, and it still works almost perfectly. The analog computer:
58
175
22
1,126
46,941
Kilian retweeted
Fourier wrapped a signal around a circle in 1822. Every Spotify equalizer, every noise filter in your AirPods, and every frequency layer inside ChatGPT runs on what he found. The trick is simple. Spin the signal at different speeds. When the spin matches a hidden frequency, the center of mass shifts. That shift is the answer. Claude and GPT use this same idea to separate relevant tokens from noise. 20 minutes. Bookmark & watch today. The math is older than the telephone.
8
115
5
750
57,882
BBC literally built the greatest sound library on the internet. It is called BBC Sound Effects, and it gives you access to more than 30,000 recordings from around the world. Just search any word, and it instantly finds matching sounds. You can filter them by category, duration, and even the continent where the sound was recorded. Every sound can be previewed inside your browser, downloaded, or added to the built-in mixer so you can layer multiple recordings together. And the archive gets insanely specific. You can find creaking ships, old typewriters, jungle ambience, distant church congregations, and even someone vigorously washing their hands. There is a good chance a BBC engineer recorded the exact sound you need decades before you were born. sound-effects.bbcrewind.co.u…
198
3,885
204
21,667
948,827
Vosotros sois muy jóvenes, pero el sudapollismo lo invento un señor que tenía un programa de cine que se emitía de madrugada y que según él sólo podía ser visto por un puñado de politoxicómanos insomnes. Una leyenda.
284
2,515
134
11,225
404,146
A 33-year-old woman at MIT wrote the code that ran inside the Apollo 11 lunar lander, and 20 seconds before Neil Armstrong touched the moon, her program made a decision the astronauts didn't know was happening that was the only reason the mission didn't crash. Her name was Margaret Hamilton. She led the team writing every line of code that would fly humans to the moon and back. The part almost nobody knows is that she had to fight to be allowed to do the work at all. Code in 1965 was not treated as real work. Rockets were serious. Circuits were serious. Writing code was something the men at NASA thought secretaries could do on the side. Hamilton was told this to her face more than once. So she started calling what her team did "software engineering." She used the phrase on purpose. In meetings. In memos. To force people to treat it as a discipline instead of a chore. Colleagues laughed at her the first few times she said it out loud. That phrase is now the name of the biggest engineering profession on earth. The story of what her code did on July 20, 1969 is the one every kid should be taught. Neil Armstrong and Buzz Aldrin were 3 minutes from touching down when the computer inside the lunar module started flashing an alarm. 1202. Then again. Then 1201. Five alarms in four minutes. The computer was telling the astronauts it could not finish everything it had been asked to do. The computer they were flying with had less memory than a modern microwave. Someone on the checklist had left a switch in the wrong position, and a radar the astronauts did not even need right then was flooding the computer with data. It was eating around 13% of the machine's brain at the exact moment every second mattered. In almost any other system, that overload would have frozen the machine. A frozen machine 30,000 feet above the moon means a crash. It means two dead astronauts and a third one orbiting alone above them, waiting for a signal that would never come. Hamilton's code did something else. She had built the software with a rule almost nobody in her field was using at the time. When the machine ran out of room, it would not treat every task as equally important. It would look at the list of jobs it had been asked to do, throw out the ones that could wait, and keep running only the ones keeping the crew alive. The radar was the low priority job. The landing was the highest. So the computer did what she had told it to do. It dumped the radar. It kept flying. The alarm was not a failure. It was the machine reporting that it was handling the overload exactly the way she had designed it to. Down in Houston, a 24-year-old engineer named Jack Garman recognized the alarm from a test his team had run months earlier. He shouted "Go" to the flight controller. The controller shouted it up to the crew. The landing kept going. Armstrong touched the surface with 25 seconds of fuel left. The part that gets lost in every retelling is why Hamilton had built that safety net in the first place. NASA had not asked for it. She had added it on her own, years earlier, because her 4-year-old daughter Lauren had once crashed the simulator by pressing a button during a test. The button was one the astronauts had been told they would never press. Hamilton wanted the code to survive that button press anyway. Her bosses told her it was a waste of time. Astronauts do not make mistakes. She insisted. The safety net went in. Two years later, on the way to the moon, an astronaut left a switch in the wrong position. The exact class of mistake she had been told would never happen. There is a photograph of her from that period. She is standing next to a stack of paper as tall as she is. Every page in that stack is the code her team wrote for the mission. She is smiling at the camera like she knows something the rest of the aerospace industry has not figured out yet. In 2016, Barack Obama put the Presidential Medal of Freedom around her neck and said the astronauts did not have much time, but thankfully, they had Margaret Hamilton. Every autopilot in every plane you have ever flown on uses a version of what she invented. Every pacemaker. Every self driving car. Every satellite in orbit. The idea that a machine should know which job matters most and drop the rest when it runs out of room is now the foundation of almost every safety system on the planet. She wrote it because a 4 year old crashed a simulator and nobody else thought it was worth fixing. The men in the room laughed at her for calling it engineering. Then her code was the only thing in the sky that did not fail.
204
1,726
139
5,791
384,096
A Danish engineer dropped out of university in 1979, wrote a Pascal compiler so fast it made Borland a hundred-million-dollar company, then built the language that became the backbone of Microsoft's entire software ecosystem, then built TypeScript, which became the number one language on GitHub in 2025 and most developers who use his work every day have never heard his name. His name is Anders Hejlsberg. He was born in Copenhagen in 1960, started studying engineering at the Technical University of Denmark in 1979, and left before finishing his degree because he was already building something more interesting than anything his courses could offer. He had access to a minicomputer at his high school, one of the first in Denmark to have one. He taught himself machine code, Algol, and Pascal. By the time he was supposed to be finishing his degree, he had already written a Pascal compiler from scratch for the Nascom-2 microcomputer. He released it under the name Blue Label Pascal. A small Danish software company called PolyData picked it up. Borland, the American developer tools company, found it and saw immediately what they had. They licensed the compiler, brought Hejlsberg to California, and in November 1983 released it as Turbo Pascal. The price was $49.95. At the time, most Pascal compilers cost hundreds of dollars and ran slowly. Turbo Pascal was cheap and compiled code so fast that developers could not believe it was real. One reviewer read the speed claims on the box, assumed they were marketing fiction, tested it, and then wrote that he had never seen anything like it. The product sold over one million copies. Borland became a serious company almost overnight, and Hejlsberg was the reason. He kept building. He became chief architect of Delphi in 1995, Borland's rapid application development environment built on Object Pascal. Delphi let Windows developers build full graphical applications faster than anything else available. It dominated enterprise Windows development through the mid-1990s. Teams that used it could ship in weeks what their competitors took months to build. Microsoft noticed. In 1996 they made him an offer. He left Borland and joined Microsoft, and the project they handed him was the one that would define the next decade of enterprise software. He designed C#. Released in 2000 alongside the .NET Framework, C# was built to be modern in ways Java was not. Clean object orientation. Garbage collection. Strong typing. A syntax familiar enough that Java and C++ developers could pick it up quickly but designed without the legacy decisions those languages had accumulated over decades. Hejlsberg later said one of his goals was to make the language feel inevitable, as if every decision was the only sensible one. It worked. C# became the primary language of Microsoft's entire development platform. It powers enterprise applications, game development through Unity, cloud services on Azure, and Windows applications across hundreds of millions of machines. Around 6.2 million developers write C# professionally today. Then he did it again. By 2010, JavaScript had become unavoidable. Every web application ran on it. But JavaScript had been designed in ten days in 1995 for simple browser scripting, not for building complex systems with large teams. As codebases grew to hundreds of thousands of lines, the lack of a type system meant bugs that a compiler would have caught in any other language were only discovered in production. Hejlsberg saw the problem clearly and spent two years designing a solution. TypeScript launched in 2012 as an open-source typed superset of JavaScript. You write TypeScript, and it compiles down to plain JavaScript. The type system catches errors before the code runs. Large teams can work on the same codebase without breaking each other's code. Every major JavaScript framework adopted it. Google, Airbnb, Slack, and Microsoft all moved their codebases to TypeScript. In August 2025, TypeScript overtook Python and JavaScript to become the number one language on GitHub by monthly contributors. He is 65 years old. He is still at Microsoft as a Technical Fellow. He is still working on TypeScript. Four languages. Four decades. Turbo Pascal made developer tools affordable and fast. Delphi made Windows application development accessible. C# became the backbone of enterprise software. TypeScript became the dominant language of the modern web. Most of the developers using his work right now are too young to know what Turbo Pascal was. They learned to code in languages that borrowed from C#. They write TypeScript every day without knowing who designed it. He dropped out of university in 1979 to build a compiler. He has not stopped since.
44
324
23
1,487
78,919
Kilian retweeted
IN 1986 MIT FILMED A LECTURE THAT OPENS BY TELLING YOU COMPUTER SCIENCE IS NOT A SCIENCE AND HAS ALMOST NOTHING TO DO WITH COMPUTERS 72 minutes from Hal Abelson and Gerald Sussman, the lecture an entire generation of engineers calls the one that rewired how they think. -> The line that lands: computer science is about computers the way astronomy is about telescopes. The tool was never the point. The real subject was always one thing -- controlling complexity. Everything else is detail. Forty years later it reads like a prophecy. AI writes the syntax now. What's left is exactly what they taught: taming complexity nobody can hold in their head. The language was never the skill -> the thinking was. This is where you learn it. Most people chase the newest framework. The ones who watched this think on a level frameworks can't touch. Bookmark & Watch today it, this one's a legend ↓
A DEVELOPER PROVED THAT MOST OF THE CLASSES YOU WRITE SHOULD NEVER HAVE BEEN CLASSES AT ALL 27 minutes from Jack Diederich, a Python core developer, on how much of your code is just a function wearing a costume. -> The moment it lands, the rule is brutal: if a class has two methods and one is __init__, you meant to write a function. Most people add structure to feel like real engineers. It just adds weight no one ever needed. Writing more code was never the skill -> writing less of it is. And when an AI agent happily generates ten classes for a job that needed three lines, the person who knows what to delete is the one who ships something clean. Anyone can add abstraction. Knowing when not to is the whole job. Bookmark it and Watch ↓
56
458
29
2,591
364,308
Kilian retweeted
Un desarrollador chino llamado tw93 se hartó de que sus aplicaciones de escritorio le devoraran la RAM y el disco. Abría Slack y desaparecían cientos de megabytes. Abría Discord, Notion o cualquier otra app y pasaba lo mismo. ¿La razón? Casi todas son lo mismo por dentro: un sitio web empaquetado con una copia completa del motor de Chrome (Electron). Decidió que tenía que haber una forma mejor. En 2022 empezó a construir Pake. Usó Rust + Tauri, que en vez de incluir un navegador completo, aprovecha el WebView nativo del sistema operativo. El resultado fue brutal: - Slack con Pake → 8 MB (en vez de 524 MB) - Discord con Pake → 9 MB (en vez de 265 MB) - ChatGPT con Pake → 9 MB (en vez de 260 MB) Cuatro años después, su repositorio tiene más de 51.000 estrellas en GitHub. Tiene builds listos para Grok, ChatGPT, Gemini, Discord, YouTube, Twitter y muchos más. Todo bajo los 10 MB, ligero, rápido y gratis. Y lo mejor: con un solo comando puedes convertir cualquier página web en una aplicación de escritorio nativa. No fundó una startup. No levantó inversión. Solo resolvió un problema que molestaba a millones de personas. A veces el cambio real lo hace una sola persona que se cansa de las cosas como están. Esta brutal, repo en los comentarios 👇
112
1,589
53
12,134
628,353
Algún día valoraremos este encuentro como se merece y nos daremos cuenta de que esto sí era un crossover necesario y no lo de Los Vengadores:
32
418
13
2,002
81,418
Kilian retweeted
A DEVELOPER PROVED YOU CAN FIND THE EXACT COMMIT THAT BROKE YOUR CODE IN A HISTORY OF 10,000 -- IN ABOUT 13 STEPS, AUTOMATICALLY.. 33 minutes from a Google engineer on git bisect: the built-in command that binary-searches your entire history to hunt down the one commit that introduced a bug. -> The moment it lands, "When did this break?" stops being an afternoon of guessing. You hand git a good commit, a bad one, and a test and it finds the culprit while you watch. Most people debug a regression by reading diffs by hand, blaming the obvious file, and hoping. Bisect doesn't hope. It cuts the search in half, then in half again, until only the guilty commit is left standing. Reading history by hand was never the skill -> letting git do the binary search for you is. And when an AI agent dumps hundreds of commits into your repo and one quietly breaks production, bisect is what finds the needle without you reading a single line. The bug isn't hiding. It's sitting in one exact commit. Most people just never learned to make git point at it. Bookmark & Watch it today ↓
TWO ENGINEERS SHOWED THE GIT TRICKS THAT MAKE PEOPLE THINK YOU'RE A WIZARD -- THE ONES 95% OF DEVELOPERS HAVE NEVER ONCE TOUCHED 42 minutes from Johan Abildskov and Jan Krag, bending git with custom configs, attributes and hooks most people don't even know exist. -> The moment it lands, git stops being four commands you repeat in fear. The same tool you've used for years turns out to have a whole layer built to bend to you. Hooks that run your checks before a bad commit ever lands. Attributes that end the "it works on my machine" merge wars. Config that makes the painful parts just stop happening. Memorizing commands was never the ceiling -> shaping git to do the work for you is. And while everyone else fights the tool by hand, the person who set it up right is shipping clean three times faster. Most people use 5% of git and call it a day. This is the other 95% nobody showed you. Bookmark it and Watch today ↓
24
52
1
370
37,991
A French engineer who lives quietly in Paris has spent 30 years writing software that the entire internet now runs on without knowing his name. He wrote the code that streams every YouTube video, every Netflix show, every TikTok clip. He wrote the code that runs the virtual servers underneath AWS, Google Cloud, and Microsoft Azure. He calculated more digits of pi than anyone in history. He has no Twitter. He has no marketing. He just keeps shipping. His name is Fabrice Bellard. Here is the story, because almost nobody outside the systems programming world knows what one man has built. Fabrice was born in 1972 in Grenoble, France. He studied at École Polytechnique, the top French engineering school. He never went to Silicon Valley. He never built a startup empire. He just wrote code. In 2000 he started a project called FFmpeg, an open-source multimedia framework for encoding, decoding, and streaming video. He was 28. The project did one thing nobody else had done well. It handled every video and audio format that existed, in one library, on every operating system. He led it himself for years. Today FFmpeg is the invisible engine of the internet. YouTube uses it. Netflix uses it. VLC uses it. Chrome and Firefox use parts of it. Every Android phone, every iPhone, every smart TV, every video editing tool you have ever touched runs FFmpeg somewhere underneath. If you have watched a video on a screen in the last 20 years, Fabrice's code processed it. He was not done. In 2003 he started QEMU, a machine emulator and virtualizer. He wrote it solo until version 0.7.1 in 2005. QEMU lets you run any operating system on any other operating system. It became the foundation of modern virtualization. KVM, the Linux kernel hypervisor, runs on top of QEMU. Every major cloud provider, AWS, Google Cloud, Microsoft Azure, IBM Cloud, runs virtual machines on infrastructure built around it. The Quick Emulator is the most cited piece of cloud infrastructure code on Earth. He kept going. In 2001 he won the International Obfuscated C Code Contest with a small C compiler that grew into TCC, the Tiny C Compiler. TCC can compile and boot a Linux kernel from source in under 15 seconds. In 2004 he calculated the most digits of pi ever computed at the time, using a personal desktop computer and an algorithm he derived himself called Bellard's formula. In 2011 he wrote a complete PC emulator in pure JavaScript that runs Linux in your browser, a project called JSLinux that engineers still cannot believe is real. In 2019 he released QuickJS, a small but complete JavaScript engine that fits where V8 cannot. In 2021 he released NNCP, a neural network based lossless data compressor that immediately took the lead on the Large Text Compression Benchmark. Then he turned his attention to large language models. He built TextSynth Server, a web server with a REST API for running LLMs locally. He released ts_zip and ts_sms, compression utilities that use language models to compress text and short messages at ratios traditional algorithms cannot reach. He released TSAC, a very low bitrate audio compression system. In December 2025 he released Micro QuickJS, a new JavaScript engine for microcontrollers, separate from QuickJS, designed for environments with almost no memory. Fabrice co-founded a telecom company called Amarisoft in 2012, where he serves as CTO. Amarisoft builds 4G and 5G base station software used by carriers and labs around the world. He has been running it for over a decade while continuing to ship personal projects from his own home page at bellard dot org He has no Twitter. He has no Instagram. He gives almost no interviews. His personal website is a flat list of projects with no styling, no fonts, no marketing copy. Just titles and links. A quiet French engineer who never moved to Silicon Valley wrote the code that quietly runs the internet. He is still shipping.
385
4,485
406
25,247
3,200,449
Kilian retweeted
난 게임을 즐겨하지 않는데 이런건 진짜 유익함 만원으로 데이터 센터의 복잡한 구조와 컴퓨터 인프라를 이해하는 스팀게임 : Data Center 빈 방에서 시작해서 랙 구매 → 서버 장착 → 모든 케이블을 직접 손으로 하나하나 연결해야함 실제 데이터 센터처럼 고객 트래픽을 처리하는 시뮬레이션 게임 출시 48시간 만에 180개가 넘는 리뷰가 달렸고, 플레이어들은 “최근 본 시뮬레이션 게임 중 가장 몰입감 있다”, “컴퓨팅 인프라를 이해하는 데 최고”라는 평가를 하고 있습니다.
230
2,586
288
16,044
1,365,762
I think every software engineer should watch this series... this, in MY opinion is a GREAT way to start understanding your code and what it actually does. youtube.com/watch?v=HyznrdDS…
7
31
2
249
13,150
A British biologist looked at 200,000 years of human history and found that the entire reason humans broke out of poverty was not intelligence, not language, not even agriculture, but one mechanism so simple a 6-year-old could explain it. His name is Matt Ridley. He is a zoologist by training, an evolutionary biologist by career, and in 2010 he wrote a book called The Rational Optimist that quietly argued the most important fact about human progress had been hiding in plain sight for the entire history of economics. Naval Ravikant has been telling people to read everything Ridley has ever written for the last 15 years. The reason is the argument inside this one book. For 200,000 years, anatomically modern humans walked around with the same brain you have right now. Same skull size. Same neural architecture. Same raw capacity for language, planning, and abstract thought. For roughly 190,000 of those years, almost nothing happened. Generation after generation lived and died inside the same Stone Age toolkit their great-great-grandparents had used. Then somewhere around 50,000 years ago, the line on the chart of human progress started to tick upward. Then it bent. Then it exploded. The question Ridley spent years on was the only question that mattered. What changed. It was not the brain. The brain had been the same for 190,000 years. It was not language, which had existed long before the takeoff. It was not even agriculture, which arrived only 10,000 years ago and was actually preceded by the upward bend, not the cause of it. What changed was that humans started trading with strangers. This sounds too small to be the answer. Ridley argues that it is the answer to almost everything. The moment one human exchanged a useful object with another human from a different group, something happened that no other species on earth had ever done. Two ideas that had developed in isolation came into contact. The flint knapper learned what the spear maker had figured out. The fisherman from the coast learned what the hunter from the forest had figured out. The two pieces of knowledge fused into something neither side could have produced alone. Ridley calls this ideas having sex. The phrase sounds frivolous and it is meant to. The point is that ideas, like genes, get better when they combine with other ideas from different lineages. An idea sitting inside one head, no matter how brilliant the head, eventually hits a ceiling. The same idea exposed to ten thousand other ideas does something genes do under sexual reproduction. It mixes. It recombines. It produces offspring nobody planned. The cleanest proof of this argument is the most uncomfortable case study in the book. Tasmania. Around 10,000 years ago, rising sea levels cut Tasmania off from mainland Australia. A population of roughly 4,000 humans was now isolated on an island, with no possibility of contact with the rest of humanity. They had the same brains. The same language. The same starting toolkit as their cousins 150 kilometers north. The natural experiment was now running. What happened next is something no economist or geneticist had ever predicted. The mainland Australians kept inventing. Boomerangs. Spear-throwers. Fishing nets. Bone needles for sewing fitted clothes. Watercraft with paddles. Their technology compounded slowly across the centuries. The Tasmanians went the other way. They did not just fail to invent the new tools their cousins were developing. They started losing the tools they already had. Fishing was abandoned within a few thousand years. Bone tools disappeared. Fitted clothing disappeared. They forgot how to make fire from scratch and started carrying lit firebrands from camp to camp instead, relighting their fires from a neighbor's whenever their own went out. By the time European explorers arrived in the 17th century, the Tasmanians had the simplest toolkit of any human society ever recorded. Their material culture had gone backward for 8,000 years. The archaeologist Rhys Jones called it a slow strangulation of the mind. Joseph Henrich at Harvard later proved with formal mathematical models that there was nothing wrong with Tasmanian brains. There was something wrong with their network. A toolkit requires a critical mass of people exchanging skills to maintain itself. The act of teaching a skill is imperfect. Every generation loses a small percentage of what the last generation knew. If your population is large enough and trading widely enough, those losses get caught and corrected by someone else who still remembers. If your population shrinks below a certain threshold and stops mixing with outsiders, the small losses compound until entire technologies disappear. This is the part that should haunt anyone reading this in 2026. Intelligence is not a property of the individual brain. Intelligence is a property of the network the brain is connected to. A genius in isolation will produce less than a mediocre thinker inside a dense exchange of other mediocre thinkers. The thing your ancestors needed in order to break out of 190,000 years of stagnation was not better brains. It was better connections between brains they already had. The implication for any individual is direct and uncomfortable. If you are smart and isolated, you will be outproduced by people half as smart who are connected. The most successful people in any field are almost never the smartest people in it. They are the ones positioned at the intersection of the most idea flows. They are reading more authors than their competitors. They are talking to more people from more disciplines. They are in the rooms where ideas from different lineages bump into each other. Ridley ends the book on the line that sounds optimistic but is actually a warning its this "The future will be invented by people who connect ideas, not by people who guard them."
261
2,009
380
7,434
883,630
Kilian retweeted
A man spends 50 years teaching at MIT. He knows his time is running out. So he records one last lecture — everything he knows, distilled into a single hour. He died 5 months later. This is that lecture. The most important hour you'll watch this week. 👇 Bookmark it for later
18
156
2
684
90,573