3 ms·
The sandbox is interpreting RISC-V, just very quickly. It's platform independent. I am actually making a game with a derivative of this repo, and in the server
by fwsgonzo 3y ago
The sandbox is interpreting RISC-V, just very quickly. It's platform independent. I am actually making a game with a derivative of this repo, and in the server I am building the programs at the same time as the server. Once the server starts, it loads all the programs, and then sends compressed programs to each client, so that everyone who connects has the same scripts. Easy and convenient, but most likely just that because I did it from the start.
- speps 3y agoThis is an interesting concept, getting the gameplay logic sent to the client this way. I guess it only works for simpler games so far, do you have any code examples?
- fwsgonzo 3y agoThe game is quite complex actually, but the script is not doing overmuch right now. The script is doing things that makes sense for a growing modding API, while the engine still does the brunt of the work. That said, there are functions that end up being called billions of times simply because you want that flexibility, and that's where the low latency script pays off.
- adastra22 3y agoOk… so why not send llvm bytecode? Or JVM? Or JavaScript? Or WebAssembly? Any of those would be better supported and have a faster, battle tested JIT engine.
- deleted 3y ago[deleted]
- mort96 3y agoMan it's so frustrating as an author to explain you you didn't just use existing technology X in the linked article but then be met by a flood of HN comments from people asking "but why didn't you just use existing technology X?"
- adastra22 3y ago1. I read the linked README and it did not answer these points. 2. Regardless, this sub thread isn’t about TFA.
- deleted 3y ago[deleted]
- phero_cnstrcts 3y agoFor the same reasons that I don’t write my websites in React.