Re:Replacing JavaScript Hot Path with WebAssembly
by PhilippGille on Thursday February 14, 2019 @05:56PM
(#19166884)
I would have loved to see Go included in the comparison as well. It can compile to wasm since 1.11.
[ Parent
| on HN ]
Re:Replacing JavaScript Hot Path with WebAssembly
by dassurma on Friday February 15, 2019 @03:26AM
(#19169360)
Go was pretty much a non-starter. They (currently) need a runtime which will make the file size non-competitive to the other ones. Also, since only Chrome has support for threads in WebAssembly (in Canary), we’d not be able to make any use of the concurrency.