Re: [w3ctag/design-reviews] WebAssembly Response API / Web Embedding (#167)

Taken up again at TAG London F2F:

Glad to see progress in the spec. We note `compileStreaming` and `instantiateStreaming` address our concerns about synchronous loading. We note, Chrome limits synchronous compile to specific sizes; we'd like to see this included in the standard (for interop).

We're happy to see issue https://github.com/WebAssembly/design/issues/1092, and look forward to seeing that conclude.

We have general concerns about how WebAssembly and JavaScript/DOM will interoperate in the future. While this may be a bit down the road, we'd like to see exploration of a general mechanism for JS objects to interoperate with Web Assembly (e.g., supporting JavaScript's dynamic prototype behavior, accessor/data properties, property descriptors and their states, and basic types like Array, Object, Number, etc.). Our concern is that the Web Assembly folks will focus on trying to create specific custom bridges for specific DOM features like Canvas, Web Audio, and Input (in support of some of their use cases), without spending the effort to generally support JavaScript itself. Such an effort would enable their chosen scenarios in the short term, but be a long-term friction to the web platform's desire to align DOM with JavaScript. We believe, focusing on a general interop mechanism for Web Assembly to work with JavaScript itself will also bring DOM along for the ride, and reduce friction long term.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/167#issuecomment-318321294