Josh Goebel

If we can use C11 this looks reasonable... you'd have to keep a `start` variable... and then when you need the time do the math to get the difference (with...

We should probably consider using the timekeeping mechanics of the library that has been requested at build time... and then abstract that behind a single generic `timeMs` function we own......

In quick search I think this just affects `core.c` and only in 4 places, so one could probably easily whip up and test PR for thsi: ``` /home/jgoebel/git/TIC-80/src/core/core.c: 207: return...

Yep. I already explained it above. We just need a PR to fix it. Or eventually nesbox will get to it.

> Also, a circle with zero radius shouldn't draw anything (now draws a 1px dot). @nesbox Why would this be bad? I mean _technically_ a circle with a radius 0...

Agreed, but this is much easier said than done... since you have like 10 different runtimes that all have their own states, etc...

Well, it's not a separate process... WASM3 is just a WASM virtual machine... you can definitely still mess everything up with infinite loops... but this is an annoying problem also...

> As a digression, WASM is sandboxed by design, so no need for forking there. WASM is a specification - not an implementation, so how do you mean it's sandboxed...

I think you'll need to be more explicit. Most of our runtimes are already sandboxed to the extent they do not have any access to the network, or filesystem, or...

> we can still use threads where we can't fork(). I was referring to the possibility of neither. :-) Evidently you can fix such things with lightweight single-process fibers also......