News for hackers. Stuff that matters.

A comment on The State of WebAssembly 2022.

Re:The State of WebAssembly 2022 by jkbbwr on Monday June 20, 2022 @08:34AM (#31809575)
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.

[ Parent | on HN ]
Re:The State of WebAssembly 2022 by bluejekyll on Monday June 20, 2022 @11:21AM (#31811415)
Interface types appear to continue to be making progress: https://github.com/WebAssembly/interface-types
[ Parent | on HN ]
Re:The State of WebAssembly 2022 by Jasper_ on Monday June 20, 2022 @12:59PM (#31812651)
From 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.

[ Parent | on HN ]
Re:The State of WebAssembly 2022 by pyrolistical on Monday June 20, 2022 @01:54PM (#31813351)
Don’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

[ Parent | on HN ]
Re:The State of WebAssembly 2022 by trusktr on Monday June 20, 2022 @12:20PM (#31812149)
You 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).
[ Parent | on HN ]