News for hackers. Stuff that matters.

A comment on Is WebAssembly the Return of Java Applets and Flash?. Parent comment

Re:Is WebAssembly the Return of Java Applets and Flash? by AnIdiotOnTheNet on Thursday July 26, 2018 @07:50AM (#17616689)
Alright, I'll give them that. However, I think this will, like it has with the rest of the web, lead to differences in how each browser handles the spec, various browser-specific extensions, etc. In that way, it's actually worse than having one company behind it.
[ Parent | on HN ]
Re:Is WebAssembly the Return of Java Applets and Flash? by j45 on Thursday July 26, 2018 @08:35AM (#17616906)
Wasm is the first major thing I can remember all the browsers agreeing on in a very long time, or ever.

Agreeing of course, after trying to do it on their own and then realizing they were thinking a lot of the same things.

[ Parent | on HN ]
Re:Is WebAssembly the Return of Java Applets and Flash? by SquareWheel on Thursday July 26, 2018 @09:17AM (#17617170)
>Wasm is the first major thing I can remember all the browsers agreeing on in a very long time, or ever.

Uh, flexbox, grid, fetch, service workers, even shadow DOM...? The cooperation between browser vendors has been exceptional over the last five years.

[ Parent | on HN ]
Re:Is WebAssembly the Return of Java Applets and Flash? by j45 on Thursday July 26, 2018 @09:30AM (#17617281)
Are any of those as large and potentially as broad as wasm?
[ Parent | on HN ]
Re:Is WebAssembly the Return of Java Applets and Flash? by SquareWheel on Thursday July 26, 2018 @10:19PM (#17623004)
For frontend devs, sure.
[ Parent | on HN ]
Re:Is WebAssembly the Return of Java Applets and Flash? by rusk on Thursday July 26, 2018 @07:53AM (#17616699)
The JS community currently deals with this by way of "polyfills" I wonder will such an approach be easier or harder with WASM ...
[ Parent | on HN ]
Re:Is WebAssembly the Return of Java Applets and Flash? by zaarn on Thursday July 26, 2018 @08:20AM (#17616825)
Any differing behaviour from the spec is supposed to be behind feature flags so that WASM Applications can reliably detect and use these.
[ Parent | on HN ]