Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

QuickJS Running in WebAssembly

github.com

Post reply on HN
Print view View original

1–10 of 28 posts

Re: QuickJS Running in WebAssembly

#5

Post by jitl »

auggierose wrote: post #3
pyrolistical wrote: post #2

Running user provided js in quickjs in webassembly in a worker in an sandboxed iframe on a different domain would offer many layers of security

I think that is what Figma does: https://www.figma.com/blog/an-update-on-plugin-security/

The library was inspired by Figma’s blog posts about their plug-in system: https://github.com/justjake/quickjs-emscripten#background

Re: QuickJS Running in WebAssembly

#6

Post by dang »

Related:

QuickJS JavaScript Engine - https://news.ycombinator.com/item?id=30598026 - March 2022 (67 comments)

A small but complete JavaScript engine - https://news.ycombinator.com/item?id=24867103 - Oct 2020 (146 comments)

QuickJS JavaScript Engine - https://news.ycombinator.com/item?id=20411154 - July 2019 (261 comments)

QuickJS JavaScript Engine - https://news.ycombinator.com/item?id=20404503 - July 2019 (3 comments)

Re: QuickJS Running in WebAssembly

#7

Post by auggierose »

jitl wrote: post #5
auggierose wrote: post #3

Earlier quoted context omitted.

I think that is what Figma does: https://www.figma.com/blog/an-update-on-plugin-security/

The library was inspired by Figma’s blog posts about their plug-in system: https://github.com/justjake/quickjs-emscripten#background

Ah ok, I see.

Re: QuickJS Running in WebAssembly

#8

Post by vbezhenar »

Imagine 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 hard questions. For example downloading an entire JS+HTML+CSS engine with every website is not a good approach, some caching must be done. There should not be version hell with every website asking for a different version of engine. But those questions could be approached as a more general web library issues.

Post reply on HN