Hood Chatham

I think they are even more important for games and reactive input because otherwise that input cannot be processed while Python code is running. We keep Pyodide's console in the...

For a game, I think the correct design would look like: Main UI thread listens to input events and serializes them into a `SharedArrayBuffer`. Game main loop periodically polls the...

> maybe there should be one UI with python as worker and one without If you are putting it into Python I would recommend not running it in a worker....

> - game logic and ctypes can make synchronous call to window.document if required.worker cannot. Yeah the goal of [hoodmane/synclink](https://github.com/hoodmane/synclink) is to allow synchronous calls to main thread from the...

Would be great to get this merged. Pyodide doesn't support installing packages from source distribution and we can't use make or subprocess so we can't really support it. For now...

Yeah. Our needs are specifically that we are trying to do cross-compilation. Certain packages have both build time and run time behavior. If one of these packages is requested at...

> I think one of you guys hinted at "you could just always use `runPythonAsync`" Yes. If you are ever checking something and picking either `runPython` and `runPythonAsync` it's better...

Even just checking for `await` would be a lot better than the current situation...

> `await(foo())` I guess that's valid syntax though formatters will convert it to `await (foo())`. I once worked briefly with someone who wrote all of their return statements like `return(x)`...

What about renaming that one too? I think `_updateLatex` or something in that vein is a more accurate name anyways since this function doesn't need to be called to render...