News for hackers. Stuff that matters.

A comment on Web Assembly and Go: A look to the future. Parent comment

Re:Web Assembly and Go: A look to the future by baq on Saturday June 23, 2018 @04:44PM (#17383348)
You don't throw web assembly in there and keep js, you throw js out at the same time.
[ Parent | on HN ]
Re:Web Assembly and Go: A look to the future by AndyMcConachie on Saturday June 23, 2018 @05:41PM (#17383609)
If you look at the sheer number of requests to fetch some JS from some random website happen when loading a modern web page this will not be possible. Web pages rendering depend on JS being pulled from many places, and often not under the dev's control. So we'll end up with a mix of JS and WASM whether we like it or not.
[ Parent | on HN ]
Re:Web Assembly and Go: A look to the future by tzahola on Saturday June 23, 2018 @06:20PM (#17383764)
Strange... I’ve seen plenty of “modern” websites without 3rd party JS bloat.
[ Parent | on HN ]
Re:Web Assembly and Go: A look to the future by tomjakubowski on Saturday June 23, 2018 @07:22PM (#17384006)
It would be tricky to completely throw JS away until WASM is able to call into the "browser APIs" (DOM, XHR, etc.)
[ Parent | on HN ]