4 ms·
> DOM bindings in WASM would be awesome. I would be a happy nerd if I could do all of my web dev in OCaml. DOM is not enough for that. You almost certainly wou
by ReleaseCandidat 3y ago
> DOM bindings in WASM would be awesome. I would be a happy nerd if I could do all of my web dev in OCaml.
DOM is not enough for that. You almost certainly would like to be able to communicate with your backend ;)
Here is a list of the "usual" web APIs: https://developer.mozilla.org/en-US/docs/Web/API https://developer.mozilla.org/en-US/docs/Web/API
And everything that needs network access or access to local resources (file system in the worst case) will never happen to WASM because of security considerations.
- xigoi 3y agoHow is allowing WebAssembly to use the network any less secure than allowing JavaScript to use the network?
- ReleaseCandidat 3y agoDon't ask me :). At least WASM will get DOM access (and hopefully access to similar web APIs) as soon as the GC is stable and usable. Once GC is supported, WebAssembly code would be able to reference and access JavaScript, DOM, and general WebIDL-defined objects. https://webassembly.org/docs/web/ https://webassembly.org/docs/web/
- lxgr 3y agoThe issue here is the same-origin principle, which rules out most low-level networking (since you could just bring your own SOP-ignoring HTTP client). Personally I think that enforcing the SOP at all cost (and even when no cookies or other authentication headers are injected by the browser) is misguided at this point and holding back modern webapps.
- sebastianz 3y agoBut you will be able to do network access though the fetch API, and fs access though its own API.