Josh Goebel

> You cannot use fibers for that, as they are not preemptive. They don't have to be preemptive, you yield once in a blue moon inside loop constructs. As I...

> , when you externally make one task yield to another task, Preemption is when a task is forcefully interrupted. Although I guess if you're using the work "make" there...

> Well, that's what we want to mitigate after all: infinite loops. But in this case the "your software" was referring to TIC-80 and WASM3... assuming WE have no major...

> Someone is going to have to maintain downstream patches for each of our VM's, It's a _very trivial_ patch, and not all of the VMs even require patching. I'm...

FYI: This isn't an argument against sandboxing other than to say "it's not needed to handle VM infinite loops well". That's a very big hammer for a tiny spinner of...

> I'm mainly interested in sandboxing as a security feature here. I hear you. I don't really see that happening unless someone comes along whose interested in the coding, not...

> I disagree, fixing Lua alone would further push other languages towards being second-class citizens. I wasn't saying **only** fix it, just that we can fix them individually.

And with 1.0?

This shouldn't be possible. Unless @nesbox changed things there is ony 96kb of MMIO RAM for scripting runtimes, with only the WASM runtime having access to a full 256kb. That...

Now I'm already on record as saying I think the full 256kb should be opened up for all runtimes (to allow copying RAM around to do advance things with graphics)......