execve("/usr/bin/ls", ["ls"], 0x7fff7e969540 /* 110 vars */)
Some how it figures out how to implement `ls`. That indeed shouldn't be possible. It puts an AI skeptic into believing we're in post-AGI territory here.Edit: tbf, I did not notice they replaced `ls` with `lol` in the trace file to avoid this, but still. To think the strace of ls was never part of the training data of the LLM then to think that is enough to somehow reverse engineer what binary blob is is insane thinking https://github.com/ghuntley/strace-to-application/blob/trunk...
* if you don't know what `ls` is, just think like implementing the simplest possible application that's 2 or 3 lines of code.
Jumping from "oh my gosh you can (incorrectly) reimplement ls from a trace of syscalls" to "this means the end of binary blobs" is a level of detachment from reality I've most recently seen from Geoff Lewis. Never mind that the author mixes up eBPF tracing and strace.
Do I have to do all the skepticism myself? FFS!
Is it a new marketing strategy to start by saying you're "incredibly cynical" about something that you're going to say the exact opposite about, perhaps to mask arguments with little rigor?
This was underwhelming, but I like his websites styling.
shric•5h ago
I tried a similar test using Python and Claude Code and it generated something that outputted a sorted list of directory contents, like ls.
However, unlike the author, this doesn’t lead me to think this is AGI. How many posts are there out there that these models would be trained on have people explaining strace outputs and comparing code to them?