Software enthusiast | Scientist | @Java_Champions | Personal account, not the views of my employers | https://xitter.cf/t.co/ZA6mcLwdlX

Tassin-la-Demi-Lune, France
Joined August 2008
Every day we are fighting to prevent French stats from looking like this.
Every day we are fighting to prevent American streets from looking like this.
2,086
4,399
410
42,250
1,446,634
Julien Ponge retweeted
Replying to @arthurmensch
6
63
2
1,844
36,816
Julien Ponge retweeted
We serve those as well! Sorry if using nuclear energy is a real blocker
POLITICOEurope
@POLITICOEuropeOct 8
Berlin-based search engine Ecosia, used by government services, is dropping its French AI partner, Mistral, its CEO told POLITICO. The company will now bet on open-source models, including those from China. vist.ly/5mh5y
181
464
41
5,933
363,564
Julien Ponge retweeted
From the person who slop-ported a screensaver to asm because he didn't know SIMD existed, and then slop-ported his shitty chat to Rust so that it drops connections and only delivers 1% of messages (after 300 commits), and doesn't know it.
Hard to know whether to laugh or cry.
5
15
3
556
17,000
Julien Ponge retweeted
I still can’t wrap my head around the fact that people get famous for writing markdown files, calling them engineering skills and putting them on GitHub 🤣
104
58
28
1,133
159,137
Julien Ponge retweeted
Replying to @Joshua_Skootsky
Some bash scripts with brutal security exploits isn’t making a new OS.
3
2
172
18,280
Julien Ponge retweeted
did you try having DHH rewrite it in Assembly?
13
14
6
1,451
40,557
The stealth company I co-founded has a name: Hadronic. Java has a strong future, AI and agents are here to stay, and the best way to predict this future is to invent it. Why, and who we are hiring: emmanuelbernard.com/blog/202…
5
22
1
74
7,300
Julien Ponge retweeted
Replying to @codemullins
😂
12
13
1
447
10,013
Julien Ponge retweeted
He discovered Rails is slow today
Been running a beta version of Campfire rewritten in Rust today! The code itself is still ugly as sin, and 6x as verbose, but the conversion was free*, and I never had to look at the Rust directly, so this is awesome 🤩 github.com/basecamp/once-cam…
39
69
2
1,786
133,551
Huge thanks to everyone! It’s official, I’m now a @Java_Champions. 🥳 So grateful to this amazing community and everyone who supported me. Let's keep coding and sharing! All the details here 👇 david.pilato.fr/posts/2026-0…
8
4
1
66
2,019
Julien Ponge retweeted
I'm looking for my next role, in Montreal or remote! My background spans compilers, systems, and AI research. I'd welcome introductions, leads, or a repost to help spread the word ❤️ More details about my experience and what I'm looking for: pointersgonewild.com/2026-09…
20
117
9
596
100,506
Julien Ponge retweeted
I have to block the actual crazy clown because it’s gotten too mean and hateful for my taste and I can’t respect someone who has to make other people feel bad to elevate themselves.
9
2
166
14,499
Julien Ponge retweeted
Linux on the desktop can’t be conquered by some elegant install scripts. This is extremely naive. There’s a lot of hardware especially consumer hardware that just doesn’t work at all on Linux or is wonky as fuck. This is a tremendous hill to climb.
100
14
10
326
25,539
Julien Ponge retweeted
Replying to @cortisquared
Globalement ce que raconte Janco a un socle scientifique... qui date de 1970 (le rapport Meadows), un poil daté. Quant aux conclusions et extrapolations, ça manque un peu de sérieux, surtout quand Janco raconte n'importe quoi sur le numérique...
1
1
7
2,209
Quand on est la première banque des Français, on ne laisse personne tomber. Et surtout pas Cédric. #NewProfilePic
321
1,550
277
21,624
1,900,438
Julien Ponge retweeted
John Carmack
@ID_AA_CarmackJun 8
I admire Fabrice Bellard. He is almost certainly a better overall programmer than I am.
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.
145
704
72
10,801
681,894
Julien Ponge retweeted
I've got an agent in a loop optimizing a renderer with the goal to minimize frame times (and tests to measure). It got times down from 88ms to 2ms and allocations down from ~150K to 500. Sounds good, right? Wrong. This is exactly why agent psychosis is a big fucking problem. As an experiment, I rewrote the Ghostty core render state in Go, with access to identically laid out data structures as Ghostty and the exact same validation tests. I made a purposely naive renderer (simple, correct, but slow). 88ms per frame with 150,000 allocations (horrendous, lol)! I then kickstarted a Ralph loop to bring the frame times down. I told it it can't modify input data structures or the public API or tests (they're correct), but it can do anything else it wants. It got to work. It has worked for about 4 hours. I've spent around $350 on this experiment so far. The results? 88ms => 1.5ms 150K allocs => ~500 allocs Incredible right? Nope. My hand-written renderer I ported has frame times (same benchmark) of ~20us (0.020ms) and 0 allocations in the update path. This is the problem with psychosis and lacking systems understanding. If you don't understand the system, you're going to accept that this is an incredible result. If you understand the system, you'll see better solutions immediately and can do roughly 75x better on throughput. The people who blindly trust agent output are in the former camp. They're sheeple, overdrinking from a fountain of mediocrity. Standard disclaimer: I use AI all the time. I like AI. The point I'm making is to not blindly accept results. Think. Analyze. Learn.
336
1,184
264
10,634
999,303
Julien Ponge retweeted
One of the problems with AI coding is that the narrative on X (and other social media platforms) is mostly set by people who don't have the deep coding and software engineering experience of the likes of Bjarne Stroustrup. Meanwhile the fundamental problems remain unaddressed: 1- AI generates super-human volumes of code 2- The code can be buggy, have security holes, be inefficient, etc. 3- The person who owns the code can be mostly unaware that such problems exist, so they won't even go after fixing them 4- The people who can actually fix the code (i.e., the software engineers who understand design, architecture, security best practices, etc.) are so overwhelmed that some of them will give up Meanwhile, AI companies are constantly pushing the narrative that you don't need to look at the code and the AI will fix everything itself. What they don't tell you is that if your code fails, you'll be held accountable, not them.
Creator of C++, Bjarne Stroustrup: AI-generated code isn't ready — it generates more bugs, more bloat, more security holes, and is nearly impossible to validate "senior developers are already retiring rather than deal with it" The problem is that even a small prompt change can shift the entire codebase in unpredictable ways
95
219
27
1,652
168,735
Julien Ponge retweeted
I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out. I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really). It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely. The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture. We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying. I worry.
501
1,891
394
15,241
1,624,488