5 ms·
Without interface types to unify passing strings around or more complex handles to resources. WASM is going to be rough on the serverside. I still have not fou
by jkbbwr 4y ago
Without interface types to unify passing strings around or more complex handles to resources. WASM is going to be rough on the serverside.
I still have not found a consistent way to construct a sqlite connection, pass it to wasm (language agnostic) and then return and close it.
- bluejekyll 4y agoInterface types appear to continue to be making progress: https://github.com/WebAssembly/interface-types https://github.com/WebAssembly/interface-types
- Jasper_ 4y agoFrom your link: > Note: This proposal is currently inactive, with work having moved on to the component-model repo. This is never getting done, is it... this is the fourth rewrite of such a feature.
- pyrolistical 4y agoDon’t be so dismayed. I’ve been following the progress and the move was a good one. It allows them to ship the thing most people care about. These things take time. If all else fails just write a polyfill. Component model doesn’t add anything new runtime requirements that can’t be polyfilled
- trusktr 4y agoYou can do that with bindings currently. Interface types should only make it easier (for languages with utf-8 strings, as interface types does not support WTF-16 strings like in Java or JavaScript yet).