emsdk VS pyscript

One place that I’ve found some real, open source unit tests to look at for an example is in the emsdk for emscripten: https://emscripten.org

Your default path was set by emsdk, given where the path is pointing. Your modified path is the path the installer linked in the Godot docs sets, just typically that kind of stuff doesn't override existing variables. This is a good thing to keep in mind in general as if you end up having to use a different version for something else in the future and just install it expecting the installer to update it for you, you will likely run into the same issue.

Emscipten C/C++ to WebAssembly compiler.

I am playing around with Emscipten which wraps around clang to compile C/C++ code in WASM binary and provide some glue-code API to embed WASM binary into JavaScript. Look into MDN Docs and Emscripten SDK to get started.

Elm is a different approach that compiles into JavaScript. In the extreme case, you have Emscripten which will compile many language into JavaScript but will feel really clumsy compared to using JavaScript in a lot of cases.

https://emscripten.org/ ?

SQLite is a pretty popular database and it's a critical dependency for many different applications. By compiling it to Wasm32-wasi, you can add it to any WebAssembly module.

This enables a new set of possibilities for Wasm and SQLite. For example, now you can run a full WordPress application in the browser [1][2] / server [3] using the same Wasm module. Note that for the browser these projects use Emscripten [4], but in the future the same Wasm32-wasi module will work.

In general, any environment that includes a wasm runtime can potentially run applications that uses SQLite under the hood. Before, it wasn't possible.

- [1] https://wordpress.wasmlabs.dev/

- [2] https://developer.wordpress.org/playground/demo/

- [3] https://wasmlabs.dev/articles/running-wordpress-with-mod-was...

- [4] https://emscripten.org/

The emscripten interface for the assimp library. It runs entirely in the browser, and allows you to import 40+ 3D file formats and access the result in JSON or glTF format. This is not a full port of assimp, but an easy to use interface to access it's functionality.

Three.js is written in JS and loads like a JS library on a modern website. Godot is a binary application transpiled to WASM (with the help of emscripten), resulting in a pretty large initial payload. Godot provides JS integration, but it feels less "native" with its layers of abstraction.

You are right for the most part. I attended a talk about pyscript[1] (runs python in the browser using wasm which is similar) and there is a 2x performance hit.

[1] https://pyscript.net

PyScript maintainer here - I'd love to hear more about this application! Either here, or over on our Discord (invite link is on the GitHub Page [1]).

[1] https://github.com/pyscript/pyscript?tab=readme-ov-file#summ...

For the first question - why your code previously created an HTML node but now just prints out the literal characters of the HTML - that was a change made in 2022.12.1, in Pull Request 915 to be specific. You can check out the single-line change that caused this, if you want. Essentially, calls to Element.write() or display() have their contents escaped by default, which wasn't the case before.

Note that in the current release (2023.03.1 at time of writing), py-[event] listeners are only hooked up once at page-load time, so changing that attribute after the page loads won't do anything. In the upcoming release, py-[event] handlers are dynamically attached and managed each time a py-[event] attribute on the page is changed. (PR 1435)

PyScript started as a usability layer around Pyodide for those not used to working in JS. It's now working on things like incorporating the Micropython runtime as an alternative, moving the interpreter to a worker thread, adding a plugins ecosystem, easier events API's, and more.

Some answers: https://github.com/pyscript/pyscript/discussions/1414

You can also check out the WebGL demo from the PyScript examples, which uses Thee.JS.

Mainly, the pys-onClick syntax that was present in earlier version in favor of the new py-* syntax, where * is a browser event name. It also takes a string of executable python instead of the name of a Callable. So in your case, you'd use py-click="get_input()". (There's a long-in-progress PR on GitHub with more examples.)

PyScript ? This is still experimental.