Hacker News Reader

Your complaints have little to do with wasm; as the post says it has no direct access to the DOM.

wasm is only supposed to speed up heavy computations like those needed to decode and rasterize the PDF, modifying the page is still done through javascript.

View on HN

Yup there's zero reason this couldn't just output a dom manipulation via FFI into straight JS code. It's fairly straightforward to do with wasm/asm.js.

Just curious: Has anyone does this yet? Specifically, I'm thinking of something vdom-like with the possibility of callbacks into wasm. Obviously, they would have to go some type of string marshalling and "proxied" IDs for callbacks, but the applications I'm thinking of don't require "huge" performance.

Yup, you call a c function that calls out to JS and then make whatever dom/canvas calls you want.

Do you happen to have a link to an implementation for wasm?

Not publicly, the emscripten docs covers it in pretty good detail:

http://kripken.github.io/emscripten-site/docs/porting/connec...

Reply on news.ycombinator.com