wasmedge-quickjs VS wasmedge_wasi_socket

I'm impressed you're already leveraging the component model. I thought it wasn't quite ready for primetime yet, but it seems you're proving that wrong... I'll have to dig in more here, as I'm working embedding WebAssembly in a high performance storage engine.

Thanks for the notes! I hear you on QuickJS - I've seen approaches of folks trying to build more node compatibility on top of quickjs (ala https://github.com/second-state/wasmedge-quickjs), but have recently heard about spidermonkey in wasmtime. Do you have intuition for nodejs vs browser in terms of what people want in terms of compatibility?

"A high-performance, secure, extensible, and OCI-complaint JavaScript runtime for WasmEdge. Run JavaScript in WebAssembly" wasm-edge-quickjs

See potential problems #1 for its proposed changes https://github.com/second-state/wasmedge-quickjs/pull/82#iss...

https://github.com/second-state/wasmedge-quickjs/pull/82#iss...

Try the bot on a PR you're interested in:

I can conceptualize a way to convert JavaScript source code to WASM then convert WASM to C source code. I have considered just using WASM, however, that introduces yet another runtime to manage https://github.com/second-state/wasmedge-quickjs.

Technically you can create a C shared object and import that shared object into QuickJS, see https://github.com/rsenn/qjs-modules, also https://github.com/second-state/wasmedge-quickjs.

That was achieved with QuickJS here https://bellard.org/jslinux/vm.html?url=alpine-x86.cfg, and here https://github.com/second-state/wasmedge-quickjs.

WasmEdge provides excellent support for JavaScript, including ES6 and NPM modules, async networking, the fetch API, React SSR, and even mixing Rust code with JS code. https://github.com/second-state/wasmedge-quickjs

https://github.com/WasmEdge/WasmEdge/tree/master/plugins/was...

A good example of WasmEdge 0.12.1 WASI enhancement is the ability to limit the Wasm app to read-only access to files and folders.

WasmEdge sockets API is refactored in 0.12.1 to be compatible with the much more limited WASI socket proposal. WasmEdge sockets have become a super set of WASI sockets.

The WasmEdge networking sockets got new features in version 0.12.1, such as DNS, network device binding and TLS. You will be able to create sophisticated microservices that require highly-efficient non-blocking network sockets. https://github.com/second-state/wasmedge_wasi_socket

Here are several complex networking applications possible with WasmEdge sockets.

I tested some simple things with wasmer, and it looks pretty good, the problem is that plugins are completly isolated from the world. This might be exactly what other people are searching, but i want the plugins to be able to open a TcpSocket, read a file, or whatever. I'm aware that i could write my own API for that, like this one.

First, let’s build a WebAssmbly-based JavaScript interpreter program for WasmEdge. It is based on QuickJS with WasmEdge extensions, such as network sockets and Tensorflow inference, incorporated into the interpreter as JavaScript APIs. You will need to install Rust to build the interpreter.