WebAssembly 101: A developer’s first steps

Re:WebAssembly 101: A developer’s first steps by mbrock on Wednesday June 07, 2017 @11:06AM (#14507027)

WebAssembly in itself is not an enemy of freedom, as even Richard Stallman would agree.

The bigger problem, which is also a problem with web scripts in general, is that browsers and script distributors generally make no effort to inform users about what scripts are running, whether they are proprietary or free software, etc.

Mozilla should fix this!

[ Parent | on HN ]

Re:WebAssembly 101: A developer’s first steps by jononor on Thursday June 08, 2017 @01:27PM (#14515633)

I wish that:

- Wasm (and JS) should have metadata (loadable before executing the code) declaring the license, and pointing to the source

- Browsers should whether site is open source (per OSI), and allow to block non-open JS. Or fake access to any sensitive APIs for non-open code (can still do DOM interactivity)

The builds should ideally be reproducible, and community-based third-party sites verify the output comes from said source. This would be another badge/warning/setting.

[ Parent | on HN ]