WASM wrapper

[tperry2x]

Off the back of the bit-rot topic, I've been looking into Paul's WASM suggestion.
Digging a bit deeper into it: (this is from Gemini, and Deepseek - so take it with a pinch of salt as it may not be correct).

1. Running WebAssembly Offline in a Browser

• WebAssembly modules (.wasm files) can be loaded and executed entirely within a web page, using JavaScript.

• If the web page is stored locally (file:// protocol) or served from a local web server (e.g., using Python's http.server or Node.js), it will work without an internet connection.

• Browsers like Chrome, Firefox, Edge, and Safari support WebAssembly natively.

2. Running WebAssembly Locally Without a Browser

• Wasmtime: A lightweight Wasm runtime for running .wasm files on desktops.

• WasmEdge: Optimized for IoT and cloud applications but works locally too.

• Wasmer: A runtime that allows running WebAssembly programs like native executables.

• WASI (WebAssembly System Interface): Provides system calls to WebAssembly, allowing it to run outside the browser with access to files, environment variables, and networking.

(I'd never heard of any of those suggestions, so I'm off to check them out).
The 'AI' algorithms go on to say:

Key Considerations

• No Internet Required: As long as the necessary .wasm file and JavaScript loader are available, execution is completely offline.

• Local Storage: WebAssembly can access IndexedDB, localStorage, or File API in a browser for persistence.

• Performance: Near-native speeds, making it a good choice for local applications.

Emphasis mine. 'Near-native speeds' which means slower. I wonder how much slower?