News for hackers. Stuff that matters.

A comment on WebAssembly First Public Working Drafts. Parent comment

Re:WebAssembly First Public Working Drafts by kllrnohj on Thursday February 15, 2018 @09:11PM (#16389386)
> Plus, it gives (or will give) much lower-level access to features like threads and memory allocation.

There's no reason JavaScript couldn't just have those features. It already has some amount of memory allocation control via ArrayBuffer & DataView.

[ Parent | on HN ]
Re:WebAssembly First Public Working Drafts by imtringued on Friday February 16, 2018 @06:34AM (#16391617)
You're describing asm.js which had significant issues as a compilation target. The generated javascript code was massive and it took several seconds just to parse it.
[ Parent | on HN ]
Re:WebAssembly First Public Working Drafts by caseymarquis on Friday February 16, 2018 @08:31AM (#16392161)
Related is a mozilla post on streaming wasm for big performance gains: https://hacks.mozilla.org/2018/01/making-webassembly-even-fa...
[ Parent | on HN ]
Re:WebAssembly First Public Working Drafts by kllrnohj on Thursday February 22, 2018 @11:54AM (#16438987)
asm.js never added threads, which is a far bigger performance issue than fine-grained manual memory allocation is.
[ Parent | on HN ]