Hacker News Reader

Indeed, webassembly is moving extremely slowly. I started a project years ago expecting https://github.com/WebAssembly/memory-control/blob/main/prop... and https://github.com/WebAssembly/memory64 to be fixed at some point. Neither are yet, and the project still suffers from it to this day.

I think wasm is still great without these fixes, but I have lost confidence in the idea that wasm will reach its full potential any time soon.

View on HN

https://github.com/WebAssembly/memory64/blob/main/proposals/...

For your second one, it looks like it is already implemented in Chromium and Firefox but not Safari. Sadly, it's not new for Apple to be dragging their feet on moving web standards forward.

It took what seems like a decade to get proper WebRTC support in Safari.

Eventually people will realise its potential is being yet another bytecode format, with VC trying to capitalise products on top of it.

Assembly is not bytecode! V8 already has bytecode for the web. WASM is meant to run faster and more efficient computations.

Dude first learn what you are talking about.

> WebAssembly (abbreviated Wasm) is a binary instruction format for a stack-based virtual machine. Wasm is designed as a portable compilation target for programming languages, enabling deployment on the web for client and server applications.

https://webassembly.org/

Reply on news.ycombinator.com