Bringing the web up to speed with WebAssembly

Re:Bringing the web up to speed with WebAssembly by Animats on Friday September 22, 2017 @02:13PM (#15314422)

I suspect that the use cases for WebAssembly will be something like this:

- < 10% user-beneficial compute in the browser

- 60% ad and tracking obfuscation

- 20% annoying scrolling and transitions

- 10% hostile code

[ Parent | on HN ]

Re:Bringing the web up to speed with WebAssembly by justinpombrio on Friday September 22, 2017 @02:16PM (#15314442)

That's about the breakdown for Javascript too, right?

[ Parent | on HN ]

Re:Bringing the web up to speed with WebAssembly by Animats on Friday September 22, 2017 @03:14PM (#15314916)

Probably, but only the first use case needs more performance.

[ Parent | on HN ]

Re:Bringing the web up to speed with WebAssembly by CaptSpify on Friday September 22, 2017 @02:38PM (#15314618)

It's frustrating to watch because it feels like we've learned nothing from the past 10+ years of web development.

[ Parent | on HN ]

Re:Bringing the web up to speed with WebAssembly by primeblue on Friday September 22, 2017 @04:00PM (#15315279)

We've learned JavaScript is a toy

[ Parent | on HN ]

Re:Bringing the web up to speed with WebAssembly by na85 on Saturday September 23, 2017 @06:57PM (#15322234)

Can't be overstated. Web assembly is going to be a disaster for users in the long run.

The helpless feeling as a bunch of people actively destroy the web for no reason other than that it's more convenient for them is so frustrating.

[ Parent | on HN ]

Re:Bringing the web up to speed with WebAssembly by userbinator on Friday September 22, 2017 @09:50PM (#15317565)

Add DRM to the 60% and I'd agree.

[ Parent | on HN ]