Nope.
000001?
Nope.
...
000000 00001 00010 00110 00000 100000?
Hey, we've got addition!
But I hope you all realize that the programming language of the future is going to be for LLMs. It'll tightly optimized for LLMs and we'll get nice tools to understand them. They'll probably be great, with loads of fancy tooling.
Any other way of coding will be considered ridiculous (except maybe if you do it for a hobby).
Better start learning Haskell, folks.
But as AI proliferates and gets cheaper, why not pay to diff files. It will be sufficiently cheap.
Sufficiently massaged OCaml/F# approaches straightforward readability in plain English.
And, for people who have been doing it for a minute, the other ways of programming do seem a little ridiculous ;)
The boat's here. Nobody's going to be programming the old fashioned way anymore (except as a hobby or a specialist). You should probably get ready for the boat.
I haven't looked into it properly but, it looks like it might actually be the same amount of tokens? (Excepting stdlib boilerplate etc.)
If that's what you assumed, the DeepSeek reasoning trace shatters that illusion. It's just disassembling by hand like what a human reverse engineer would do if you (sadistically?) denied them a disassembler. Yeah, the human reverse engineer would need an excellent memory of the x86_64 instruction reference, but we already know LLMs can recall a breadth of information. What we don't know, that this article also provides no evidence for, is if there will be any benefit in using the LLM for this over objdump.
The article seems to intentionally conflate disassembly (computationally cheap) with decompilation (can be computationally expensive) to imply that there's some benefit to asking the LLM to work with machine code (seems impressive to the RE layman) rather than working in assembly (something you probably already assumed LLMs can do,) but the DeepSeek trace has a disassembly in it, and it's hard to imagine that inference will ever be cheaper or more reliable per-token than objdump is at producing the same output.
And the proof of course is that I can reassemble/link, with "modern" tools, their presented assembly and it combines right back into a hex dump mirroring the original.
Anyway, it's been a joy to take the long-out-of-print book, "The First Book of KIM", and re-typeset it (re-assemble it?) for modern hobbyists like myself. LLMs have allowed me to clean up the poor OCR-extracted text from the original. Claude has not only done that, but found missing labels and "equates" in the assembly, as legitimately printed in the book—not OCR errors.
Heck, Claude latched on to a bug in the classic "WUMPUS" game that apparently the author was not even aware of. (But I left that bug in for hobbyists to find—or exploit.)
This process would normally require a human to lift bytes -> ASM, ideally ASM -> obfuscated source, making sense of it, and doing the chain backwards, and it requires coordinating a lot of knowledge. Which of course is no problem for an LLM.
They don't list any model size or version that failed, right?
PS: and it also has no problem writing a simple 'bouncing sprite' C64 demo without going through assembly and wrap that in a .prg file (of course this is basically the 'hello world' of C64 demos and could be as-is in the training set).
Let's see if the data URL survives HN:
https://floooh.github.io/tiny8bit/c64.html?file=data%3Aappli...
Pet peeve: Using AI to solve problems that existing algorithms can dependably solve with 10^-6 the CPU resources.
[0] is the episode I'm referring to, but the whole series of videos about his woes with this bike are quite interesting.
There's certainly eg open source audio dev material out there but not nearly as much as web dev. How else do you explain all the avalanche of vibe coded audio plugins and DAWs appearing this year?
I would assume that to a LLM, a binary executable is not much worse than actual source code. And it's much denser, just missing the semantics of human-written identifiers. It's the code's pure logic, condensed into machine language.
And there's tons of it, many vendors supply it "freely" (you don't need license keys to train on a binary) It's often battle-tested code that you wouldn't get hold of otherwise, and compared to ingested source code its unlikely that Codex regurgitates a recognizable part of a Windows 2000 DLL into your C++ source code.
Executables are often larger than their source code.
A toolchain that creates repeatable binary builds is difficult to create. And a nonrepeatable build is potentially nondeterministic, in the sense that uncontrolled or hidden inputs impact the output.
Makes complete sense to study things people actually want to use and consume
If it works and it's verified in nine different ways, throw it in the training pile, and then automate the process.
By them being nothing special?
> appearing this year?
Vibe coding in general became viable last year, Opus 4.5 is Nov 24, 2025.
I've made a bunch of unreleased vibe-coded VST plugins to replace the hundreds that I've bought over the years - and many of the barriers to development weren't the model. Just having belief that the model was capable of the work, a bit like the 4-minute mile. Also knowing to persevere and iterate with the model, not giving up because the first UI is inevitably so amateurish.
There's also a flywheel happening. If you make permanent notes on the process, your rules for UI design, a library of re-usable components and algorithms, tools so the model can judge its own work... the whole process for the next VST just gets much faster & much easier. Same goes for any software you make with AI too.
As of this fall, you are being professionally irresponsible and SHOULD NOT be working in the field if AI is not integral to your SDLC. At a minimum it should be checking your code for bugs and vulnerabilities.
You don't need software for that aside from the compiler/linker tools (which are free for C/C++ compilers, rust, etc.). You can then permutate/generate the source code using tools/techniques like fuzzing.
There's also things like Intel's instruction set documentation.
https://arxiv.org/html/2403.05286v2
"Hello, we're here to see whether or not your fridge is runni-Hey, no not like that, this is serious!"