Web Assembly Working Group Charter Approved

Re:Web Assembly Working Group Charter Approved by sqeaky on Friday August 04, 2017 @01:39PM (#14930407)

I agree with most of what you say but it is a bit extreme to say "Unless you write compilers, nothing changes".

Some troubleshooting methods will change, the ability to view source will be reduced, performance will be increase, safety will increase...

And many more subtle things. I agree it is a huge win, but there are some (minor) negatives.

[ Parent | on HN ]

Re:Web Assembly Working Group Charter Approved by baybal2 on Saturday August 05, 2017 @03:53AM (#14934671)

There is a major negative effect - you will be running obscure blobs of code - you can't think of anything worse for security.

Sandboxing as such will not help you to any degree with that. People promoting sanboxing as a universal solution have poor knowledge of computer security

[ Parent | on HN ]

Re:Web Assembly Working Group Charter Approved by TomMarius on Saturday August 05, 2017 @08:44AM (#14935433)

I don't know a complex web app that doesn't minify and/or obfuscate its source code.

[ Parent | on HN ]

Re:Web Assembly Working Group Charter Approved by baybal2 on Saturday August 05, 2017 @03:08PM (#14937328)

You do not see a difference in between two?

[ Parent | on HN ]

Re:Web Assembly Working Group Charter Approved by TomMarius on Saturday August 05, 2017 @03:18PM (#14937386)

No, not at all (practically). Either way I need a source map and/or a decompiler to read the code.

[ Parent | on HN ]

Re:Web Assembly Working Group Charter Approved by baybal2 on Saturday August 05, 2017 @03:46PM (#14937522)

The parsed VM bytecode and calls to native code by the interpreter are two quite different things

[ Parent | on HN ]