QuickJS Running in WebAssembly
21–28 of 28 posts
Re: QuickJS Running in WebAssembly
#22Would you use this to run untrusted JS on the server?
Another thing is resource consumption where you likely want to limit cpu- and mem-usage.
Re: QuickJS Running in WebAssembly
#23Would you use this to run untrusted JS on the server?
Re: QuickJS Running in WebAssembly
#24Would you use this to run untrusted JS on the server?
Not sure if I'd trust the wasm runtime. If someone breaks out of that it's game over. QuickJS in a unikernel in something like Firecracker VM would be the most secure approach and still provide good performance and startup time. Another thing is resource consumption where you likely want to limit cpu- and mem-usage.
Re: QuickJS Running in WebAssembly
#25Imagine something like "base system" with WebAssembly, bare bones HTML engine with canvas support and no CSS. So now you can just download your favourite JS engine, your favourite HTML, CSS engines. But browser does not necessarily need to sheep those. It would allow to lower the bar for entry into browser market. I think that even a single person could implement that kind of base browser. Of course there're many har…
Re: QuickJS Running in WebAssembly
#26Re: QuickJS Running in WebAssembly
#27Would you use this to run untrusted JS on the server?
WASM probably doesn't add much there.
Re: QuickJS Running in WebAssembly
#28Hello, library author here. Happy to answer whatever questions you have.