It's not the wrong design; RISC-V is designed around extensions, and they left room in the instruction encoding for them. They don't have a 800-lb gorilla like Intel shoving the ISA down customers' throats (Canonical is the closet thing) so there is some debate on which combination of extensions are needed for desktop apps.

From the docs, I couldn't tell if it had disassembled very much of the EXE. Looks like it extracted most of the assets, the presence of open-source modding tools for this game in training data likely helped a bit.

Realize, though, that just grabbing a frame buffer is not a thing anymore. To render graphics you need GLES support through something like ANGLE, vectors and fonts via Skia, Unicode, etc. A web browser has those things. Any static binary bundling those things is also gonna be pretty large.

And JavaScript is very good at backwards compatibility when you remove the churn of frameworks (unfortunately Electron doesn't guarantee compatibility quite as far back)

That policy doesn't explicitly disallow writers from using LLMs as part of their process, nor does it mention reviewing submissions for content that could be LLM-generated.

I like some of the ideas in the article but there are some very "it wasn't just A, it was B" sentences in there. IEEE has a higher standard.