News for hackers. Stuff that matters.
Re:Compiling JavaScript to WASM or ASM.JS with NectarJS and ... by danjoc on Friday March 10, 2017 @05:02PM (#13842555)
>No need to obfuscation

Suddenly, the web is no longer open to inspection. I was so eager to see any language other than JS on the web, I didn't realize what wasm really meant until just now. I know where this is going.

Re:Compiling JavaScript to WASM or ASM.JS with NectarJS and ... by TomMarius on Friday March 10, 2017 @06:53PM (#13843175)
While I know it's nice that you could open the source and explore, I don't see how people could value it above all the upsides WebAssembly is bringing us.
Re:Compiling JavaScript to WASM or ASM.JS with NectarJS and ... by danjoc on Saturday March 11, 2017 @11:28AM (#13845933)
Can't link resources. Can't spider it. It's going to look like native app silos. Truly, Flash 2.0. As long as wasm has no GC, and JS requires GC, I'm not sure how well this will work though.
Re:Compiling JavaScript to WASM or ASM.JS with NectarJS and ... by chrisdouay on Friday March 10, 2017 @05:13PM (#13842628)
Google Closure Compiler ? javascript-obfuscator ? Proprietary code is obfuscated

wasm is a bytecode for the web, no more, no less

Re:Compiling JavaScript to WASM or ASM.JS with NectarJS and ... by seraum on Friday March 10, 2017 @05:04PM (#13842567)
I suppose you dislike this news : )
Re:Compiling JavaScript to WASM or ASM.JS with NectarJS and ... by danjoc on Saturday March 11, 2017 @11:29AM (#13845935)
Did you like Flash? I don't think anyone misses it.