Pinned Tweet
Almost finished a task, but I need a break. Just ask Rover to finish it while you are stretching a bit 😁
Been using his emulators for long time. His projects are amazing.
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.
1
62
We started using our own assistant to help with analytics. Of course, the first step was to implement the @posthog connector in the app 😄
HolaClaw v1.2 is out. It introduces Connectors: a simpler way to add external services to your OpenClaw assistant.
Here it is connecting @posthog in under a minute.
Download it on holaclaw.ai 👋
2
78
I hope we can soon switch to use @lightpanda_io in @holaclawai !
Chromium or Lightpanda for OpenClaw?
By default, OpenClaw uses a headless Chromium to browse (300MB+ RAM). Inside HolaClaw, OpenClaw runs in an isolated VM, so resources matter. We wanted to try Lightpanda, a browser built for agents at ~24MB.
holaclaw.ai/blog/agent-brows…
1
116
You can see how we automated the E2E test suite with FlightPlanner in some of our repositories!
📄 github.com/endorhq/capsule/b…
📄 github.com/endorhq/rover/blo…
2
125
Sometimes when you have doubts about how to work with agents, asking them could give you some interesting insights.
Here you have a quick conversation with Claude about data formats capsule.endor.dev?gist=40cb2…
1
78
Sometimes, conversations with AI agents give you more insights about a code change than the code itself. We started sharing some of the sessions internally to help reviewing changes and ideas.
Today we released a way to visualize them. Free and Open Source 😄
We just open-sourced Capsule, an interactive inspector for AI coding agent sessions.
It turns the raw JSON logs from Claude Code, Codex, Copilot, and Gemini into a browsable timeline you can actually read.
🧑🚀 capsule.endor.dev
1
121
I'm impressed how disconnected is Gemini from the Google Docs suite. I tried to edit a document to find typos and awkward phrases.
It couldn't edit the document. The only action it gives me is "Instert" the entire LLM response or copy it.
It's crazy this is a paid feature
64
This was a quite interesting progress. Some people asked us how we use AI. This is the way we found more useful and valuable
We rebuilt our documentation with AI. We could tell you that we asked Rover and Claude to do everything, but that's far from reality. We used agents to write, iterate, and speed up the process, while writing the important parts ourselves.
🧑🚀 AI doesn’t replace thoughtful documentation, it amplifies it
endor.dev/blog/rebuilding-ou…
54
4. I tend to use just a "main" monitor because I had issues with my neck with some configurations like 3
50
And every new addition to your app doesn’t involve an extra fee for a new service you need to pay
So many ways to do hosting. Personally, I really like Coolify from @heyandras
coolify.io/
I'd say savings from AWS to Hetzner are about 5-10x (like EC2 to VPS)
Savings from Vercel to Hetzner are about 1000x depending mostly on your traffic
Low traffic Vercel is cheap, high traffic it gets very expensive fast
Low traffic VPS is cheap, high traffic it's still cheap
48
The basics will be always required. I know very smart people that decided to go full SQL and skip ORMs in 2025 due to low performance issues.
They are raising an amazing company. Understand your product and code. Use agents to help you building it 🧑🚀
Supabase ha sacado un curso para aprender Base de Datos PostgreSQL desde cero y paso a paso
✓ +5 horas en 39 vídeos
✓ Consultas, joins, JSON, índices y creación de tablas
✓ Todo explicado de forma práctica y progresiva
Es gratis → databaseschool.com/series/in…
1
30
Create a new llms folder in your repo and pull the libraries' docs there.
Agents will read them and find the right information when required. Since it's in the repo, it's always available and you don't need to grant extra permissions to agents 😄
30
Devoting some time to tweak prompts can improve results. However, over optimizing a prompts for a single model causes you need to update constantly as new models are published regularly.
Focus on processes and not individual prompts.
Replying to @alexalbert__
2. Tool triggering rates may change. Opus 4.5 is more responsive to system prompts, so if your old prompts used aggressive language to reduce undertriggering, you may now see overtriggering.
Dial back "CRITICAL: You MUST use this tool" to just "Use this tool when..."
40

















