Live data from Hacker News

WebAssembly 101: A developer’s first steps

blog.openbloc.fr

151–153 of 153 posts

Re: WebAssembly 101: A developer’s first steps

#151
post #143

Earlier quoted context omitted.

1. Eh, if I'm running, say, Ubuntu and haven't turned on the non-free stuff I can make some reasonable assumptions about my baseline rights. 2. I don't think anyone is claiming minified JS is awesomely transparent. WASM is certainly worse than the unobfuscated, unminified JS, which until not long ago was the norm.

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!

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.

Re: WebAssembly 101: A developer’s first steps

#153

Surprisingly I am struggling to find such essential information as where exactly is wasm supported right now. In latest Chrome? How about Edge? how about the browser on my smartphone?

CanIuse is very useful for this: https://caniuse.com/#search=wasm
Post reply on HN