News for hackers. Stuff that matters.

A comment on W3C abandons consensus, standardizes DRM, EFF resigns. Parent comment

Re:W3C abandons consensus, standardizes DRM, EFF resigns by woodrowbarlow on Monday September 18, 2017 @06:37PM (#15280305)
I think you're too quick to put DRM and WebAssembly in the same bucket. Yes, WebAssembly could lead to a future of closed-source proprietary technology on the web (and in that sense is similar to DRM), but the difference is that WebAssembly offers technical value. WebAssembly is a tradeoff for the public, whereas DRM exists strictly to restrict the public.
[ Parent | on HN ]
Re:W3C abandons consensus, standardizes DRM, EFF resigns by baddox on Tuesday September 19, 2017 @01:44AM (#15282077)
I don't really see any new threat from WebAssembly. Isn't the only threat that the same malicious code can run with better performance than JavaScript? As far as I can tell, WebAssembly doesn't provide any additional access to native system features like this DRM spec does.
[ Parent | on HN ]
Re:W3C abandons consensus, standardizes DRM, EFF resigns by gsnedders on Tuesday September 19, 2017 @07:22AM (#15283560)
WASM is strictly less powerful than JS.
[ Parent | on HN ]
Re:W3C abandons consensus, standardizes DRM, EFF resigns by baddox on Tuesday September 19, 2017 @01:36PM (#15286794)
Indeed, from what I'm reading it looks like most of the usual JS tasks (like DOM manipulation, listening to input, and network requests) still need to happen by your WebAssembly module calling out to normal JS.
[ Parent | on HN ]