Compiling JavaScript to WASM or ASM.JS with NectarJS and Running It with Node.js

#1

Post by seraum » Fri, Mar 10, 2017, 9:54 PM UTC

Compiling JavaScript to WASM or ASM.JS with NectarJS and Running It with Node.js
blog.seraum.com

Re: Compiling JavaScript to WASM or ASM.JS with NectarJS and Running It with Node.js

#2

Post by danjoc » Fri, Mar 10, 2017, 10:02 PM UTC

>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 Running It with Node.js

#3

Post by seraum » Fri, Mar 10, 2017, 10:04 PM UTC

danjoc wrote: post #2

>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.

I suppose you dislike this news : )

Re: Compiling JavaScript to WASM or ASM.JS with NectarJS and Running It with Node.js

#4

Post by chrisdouay » Fri, Mar 10, 2017, 10:13 PM UTC

danjoc wrote: post #2

>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.

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 Running It with Node.js

#5

Post by TomMarius » Fri, Mar 10, 2017, 11:53 PM UTC

danjoc wrote: post #2

>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.

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 Running It with Node.js

#6

Post by danjoc » Sat, Mar 11, 2017, 4:28 PM UTC

TomMarius wrote: post #5

danjoc wrote: post #2

>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.

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.

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 Running It with Node.js

#7

Post by danjoc » Sat, Mar 11, 2017, 4:29 PM UTC

seraum wrote: post #3

danjoc wrote: post #2

>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.

I suppose you dislike this news : )

Did you like Flash? I don't think anyone misses it.