4 ms·

I have not been able to get excited about WASM due to the poor memory management situation. It’s been years since the MVP and we are still in limbo about freei

by fayten 4y ago

I have not been able to get excited about WASM due to the poor memory management situation. It’s been years since the MVP and we are still in limbo about freeing memory. A great issue documenting a lot of the pain points around this is here: https://github.com/WebAssembly/design/issues/1397 https://github.com/WebAssembly/design/issues/1397 Until this is solved WASM is dead in the water for a huge variety of applications. I am rooting for WASM, but it has been discouraging to watch this go unsolved over the years.

capableweb 4y ago
I'm not sure I fully understand the issue here, but reading through it, it seems to point towards that this issue only happens to people using 32bit browsers? Which, I assume (depending on the environment of course), is a very small section of users nowadays.
- tyingq 4y ago
  Maybe not: https://github.com/WebAssembly/memory64/blob/main/proposals/memory64/Overview.md https://github.com/WebAssembly/memory64/blob/main/proposals/...
  - IshKebab 4y ago
    That's about 64 bit WASM not 64 bit browsers.
    - tyingq 4y ago
      It's about desktop WASM not having access to all the memory and so fine grained management of memory there could be important also.
deleted 4y ago
[deleted]
rr808 4y ago
Agreed on this, I assumed you'd be able to write for WASM with go, Java etc but no GC based languages are allowed.