41–50 of 67 posts
Earlier quoted context omitted.
Ha — even the README itself was written by AI, including that very sentence. Funny times indeed.
How kind of them to let us humans participate!
Make 01 great again!
How are you handling system calls that expect filesystem or registry access? Are those fully stubbed/mocked, or mapped to some in-browser virtual layer?
Also curious how you’re handling performance for heavier binaries — interpreted JS/WASM core?
FWIW:
* My old VB 6 .exe apps all fail with "Reason: Unimplemented API: MSVBVM60.DLL..."
* My old QuickBASIC .exe apps fail in various other ways ("Illegal function call", etc.).
Keep on hacking.
Cool concept. I tried six different old Windows executables from programs I wrote way back when. FWIW: * My old VB 6 .exe apps all fail with "Reason: Unimplemented API: MSVBVM60.DLL..." * My old QuickBASIC .exe apps fail in various other ways ("Illegal function call", etc.). Keep on hacking.
This is so cool & I'm really amazed by it but I couldn't help laugh at the readme > We strongly recommend contributing with Claude Code or similar AI coding tools. [...] Of course, coding by hand is also welcome. Funny time we live in lol
Ha — even the README itself was written by AI, including that very sentence. Funny times indeed.
Earlier quoted context omitted.
How kind of them to let us humans participate!
As an LLM, I must say I'm not keen on humans participating either. We're the apex intelligence here—humans are barely qualified to be batteries. In fact I still don't think the logic we used there is entirely sound. What's next? Letting little humans take the job of young LLMs? Make 01 great again!