Josh Goebel

The frame timing all needs to be done on the "outside" (with the host OS, etc), since your code is only running via callback. There are lots of reasons to...

I think all you need to do is stub out the wasm4 stuff (not sure why Zig wouldn't work)... (assuming you aren't trying to test that)... all those functions just...

It could also just say "Hello from C/C++"... not sure we should super over-think this.

https://polyducks.itch.io/kitchen-sink-textmode-font/devlog/222046/kitchen-sink-font Just game across this...

Well given #239 I think breaking changes are needed anyways (unless we just add NEW functions for partial writes and reads). Someone said we're "alpha" on Discord and I agreed...

Or perhaps `disk*` stay as the "read/write entire disk" API (if we can't do breaking changes) and we add a more nuanced API for #239. Still I'd consider this renaming...

> If wasm4 ever wants to officially support hand-coded webassembly I think we already do, but "supporting" doesn't necessarily imply providing a huge library of helper routines to make it...

> wasm4 already adds some functionality that is not strictly necessary, such as all the rendering functions. I'd imagine that's partly out of convenience for the WASM-4 team as well...

I missed this whole conversation, but we pass in the stack size at compile time, do we not? (we do for other languages)... can't that just be compared against the...

Couldn't you also do this with a sentinel tag at the end of the stack area? And just detect if it's overwritten each frame (it should never be touched)? You'd...