News for hackers. Stuff that matters.

A comment on Replacing JavaScript Hot Path with WebAssembly.

Re:Replacing JavaScript Hot Path with WebAssembly by Roboprog on Thursday February 14, 2019 @05:11PM (#19166571)
Too bad no wasm on IE 11

Where it would be needed most

[ Parent | on HN ]
Re:Replacing JavaScript Hot Path with WebAssembly by tracker1 on Thursday February 14, 2019 @05:19PM (#19166623)
Depends on your use case... a lot of places are just plain deprecating IE altogether.
[ Parent | on HN ]
Re:Replacing JavaScript Hot Path with WebAssembly by Roboprog on Friday February 15, 2019 @05:09PM (#19175180)
As well they should:-)

But IE 11 has been given a stay of execution until 2025 I believe.

And sadly most of my users are still on it (government and healthcare)

[ Parent | on HN ]
Re:Replacing JavaScript Hot Path with WebAssembly by ghayes on Thursday February 14, 2019 @05:21PM (#19166634)
Isn't Microsoft one of the founding companies in the initiative? [0]

[0] https://webassembly.org/

[ Parent | on HN ]
Re:Replacing JavaScript Hot Path with WebAssembly by simlevesque on Thursday February 14, 2019 @05:22PM (#19166643)
Microsoft !== IE

The logo on the front page you linked it the logo of Microsoft's other browser, Edge. There is no other mention of Microsoft or Internet Explorer on it.

[ Parent | on HN ]