God of War on PSP, recompiled to WebAssembly and running in the browser

Original Article ↗ Hacker News Discussion ↗

A new project translates a PSP-era God of War game’s MIPS machine code into C++ and WebAssembly so it can run in a browser, raising questions about where static recompilation ends and emulation begins. Commenters weigh the promise of AI-assisted reverse engineering for game preservation against concerns over legality, IP control, and a flood of low-quality “slop” ports. The thread also touches on broader industry shifts, including the impact of AI on software development practices, the economic health of game studios, and a potential move toward server-side or streamed games to resist reverse engineering.

Technical Approach & What This Actually Is

  • Project translates PSP MIPS machine code ahead-of-time into C++, then compiles to WebAssembly and runs against a small PSP OS/GPU reimplementation using WebGL2.
  • Several commenters argue this is still “emulation in spirit”: CPU instructions manipulate a MIPS CPU state + memory model, with high‑level emulation for OS/GPU.
  • Others note it’s closer to static recompilation / AOT + HLE than a traditional interpreter/JIT emulator, and is game-specific rather than a general-purpose emulator.

Quality, “Slop” Ports, and Tooling

  • Some find the result impressive, especially given how demanding PSP games like God of War used to be on desktop emulators.
  • Others criticize this style of project as “slop”: per‑game hacks, generated C++ that’s essentially structured assembly, and likely bugs versus mature emulators like PPSSPP.
  • Broader concern: rise of quick, AI-assisted ports that look good in a screenshot but are unstable or unplayable and abandoned after initial hype.

AI’s Role in Emulation and Reverse Engineering

  • AI is seen as accelerating decompilation/recompilation: working at function level, brute‑forcing C output until binaries match, or using emulators as oracles.
  • Some celebrate this as “cracking the emulation bubble” and enabling direct ports and better preservation.
  • Others worry about fragmentation (many half-baked ports instead of a few high‑quality shared projects) and about opaque AI-generated code that’s hard to maintain.

Legal, Ethical, and IP Issues

  • Repeated discussion of legality: having your own dumped ROM is argued as acceptable in some jurisdictions; distributing ROMs is not.
  • This project is noted as requiring users to supply their own PSP ROM and decryption tool; no assets are included.
  • Some foresee IP holders pushing for stricter laws or even pressuring AI providers to block reverse-engineering uses; others think “nothing will happen.”

Game Preservation vs. Control & Industry Impact

  • One camp views these tools as great for long-term playability of old games across future platforms.
  • Another notes that ISOs and emulators already exist; this is more akin to “remastering” than preservation.
  • Thread branches into worries that pervasive AI + piracy/remastering will push publishers toward server-only/streamed games, reducing consumer control, and may contribute to industry instability and layoffs.