News for hackers. Stuff that matters.

A comment on Bringing the web up to speed with WebAssembly. Parent comment

Re:Bringing the web up to speed with WebAssembly by AnIdiotOnTheNet on Friday September 22, 2017 @02:47PM (#15314706)
And how long do you think that'll last? As developers stubbornly persist in trying to make desktop applications on the web, they'll demand more and more access to the host, and browser developers will give it to them in an effort to one-up each other.

If anyone had actually cared about security on the web we wouldn't be where we are now.

[ Parent | on HN ]
Re:Bringing the web up to speed with WebAssembly by jfbastien on Friday September 22, 2017 @04:11PM (#15315369)
Your phrasing leads me to believe that you distrust how web standards organizations approve new features? If that's not the case then I invite you to join the W3C Community Group and help avoid insecure additions w3.org/community/webassembly/
[ Parent | on HN ]
Re:Bringing the web up to speed with WebAssembly by kuschku on Friday September 22, 2017 @06:30PM (#15316484)
That doesn’t help, as the browser vendors ignore the W3C entirely anyway, and just do stuff in the WHATWG.

And we already have a bluetooth stack for the web, USB drivers in JS, etc.

[ Parent | on HN ]
Re:Bringing the web up to speed with WebAssembly by jfbastien on Friday September 22, 2017 @07:27PM (#15316859)
That is entirely incorrect for the WebAssembly CG and WG.
[ Parent | on HN ]
Re:Bringing the web up to speed with WebAssembly by kuschku on Friday September 22, 2017 @08:11PM (#15317142)
The WebAssembly grouo may be different, but in every other group I've seen, the browsers simply didn't care about what everyone else was doing.

To the point that they redefined the URL spec and then complained that cURL didn't fulfill it.

[ Parent | on HN ]