tools

For whatever it's worth, this is exactly the kind of awful that I never want in any code base that I'm working on: <https://github.com/simonw/tools/blob/473e89edfebc27781b43443...> At least run a pretty-printer on the code so that it can be reviewed by anything but a robot. Part of developing a good software system is about exercising taste in vendored-in libraries and, especially, the structure around them. P.S. I've gone to look at other chunks of Javascript and see that I was unlucky to grab this steaming pile first.

That x86 machine code link reminded me of an LLM project I did just last week - https://tools.simonwillison.net/sloccount I decided to see if I could get an old Perl and C codebase running via WebAasembly in the browser having Claude brute-force figuring out how to compile the various components to WASM. Details here: https://simonwillison.net/2025/Oct/22/sloccount-in-webassemb... Here are notes it wrote for me on the compilation process it figured out: https://github.com/simonw/tools/blob/473e89edfebc27781b43443... I'm not saying it could have created your exact example (I doubt that it could) but you may be under-estimating how promising it's getting for problems of that shape.