https://github.com/desktop-cgi/bridge-wasm

wasm bridges for langauge interpretors, important c libraries, and other important libraries
https://github.com/desktop-cgi/bridge-wasm

Last synced: 8 months ago
JSON representation

wasm bridges for langauge interpretors, important c libraries, and other important libraries

• Host: GitHub
• URL: https://github.com/desktop-cgi/bridge-wasm
• Owner: desktop-cgi
• License: mit
• Created: 2023-07-04T06:04:45.000Z (almost 3 years ago)
• Default Branch: main
• Last Pushed: 2023-07-16T15:34:36.000Z (almost 3 years ago)
• Last Synced: 2025-01-17T12:34:15.363Z (over 1 year ago)
• Language: JavaScript
• Size: 448 KB
• Stars: 1
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

          
# bridge-wasm

`wasm bridges` for language interpretors like `php`, `perl`, `python`,`micropython`, `cpython`, `ruby`, `julia`, `cpp`, `golang`, `ocaml`, `lua`, `napi`, `wasm-run`, `r-lang`, `openssl`, important c libraries, and other important libraries

![bridge-wasm](./docs/Bridge-Wasm.jpg)

[bridge-wasm](./docs/Bridge-Wasm.jpg)

Expected risks or considerations for your designing for multiple interpreter designs:

- Load times (load wasm's during server start, and invoke plus run code dynamically based on need recommended)

- Memory limits, usages, leaks, and security

- Performance to OS based designs of serverless

- Performance to OS based designs of VM

- Sandboxing and security restrictions based on nodejs code

- File and OS access limitations or allowance based on runtime needs and models/ architecture

Expecting the design to replace the [desktop-cgi](https://github.com/desktop-cgi/desktop-cgi) runtime embedding design for multiple interpreted languages and databases; and hopefully other executables. 

Credit: [many wasm packages taken from @polylang.io](https://github.com/chris-koch-penn/polylang.io/tree/master/wasm)