Sneak Peek at WebAssembly Studio

Post by dmix » Wed, Apr 11, 2018, 10:09 PM UTC

haberman wrote: post #29

danShumway wrote: post #18

I think WebAssembly is one of the most exciting efforts for the web right now, second maybe only to Houdini or IPFS. I say that even as someone who works pretty much exclusively in Javascript now and who loves the language - a lower level format will be great for everyone. I can't wait for more native languages to start supporting it.

I completely agree. I remember all the years where the prevailing wisdom was "standard web byte-code isn't necessary/feasible/desirable/etc." It's nice to realize that such pronouncements aren't necessarily the final word. It turns out there is a way to give people the byte-code they always wanted. (btw I know WebAssembly isn't, strictly speaking, byte-code. It's a compact binary encoding of an AST. But it has all th…

Post by tracker1 » Wed, Apr 11, 2018, 10:29 PM UTC

Ajedi32 wrote: post #38

k__ wrote: post #12

Earlier quoted context omitted.

Really nice. I like these new in-browser IDEs. They often bring a full-fledged build system with them. Just open the URL, write your code, hit compile and download your build.

You know, now that I think about it... Node projects pretty much have all their tooling written in JavaScript already. I wonder how hard it'd be to run all that in the browser directly (right now I think this IDE is handling that on the server).

Post by [deleted] » Wed, Apr 11, 2018, 11:12 PM UTC

dmix wrote: post #62

Promarged wrote: post #32

If available it's better to use instantiateStreaming [0] for faster compilation, e.g. this: fetch('../out/main.wasm').then(response => response.arrayBuffer() ).then(bytes => WebAssembly.instantiate(bytes)) could be expressed as this: fetch('../out/main.wasm').then(response => WebAssembly.instantiateStreaming(response)) [0]: https://hacks.mozilla.org/2018/01/making-webassembly-even-fa...

Wouldn't that still require `response.arrayBuffer()`? For ex (line 2): fetch('../out/main.wasm').then(response => WebAssembly.instantiateStreaming(response.arrayBuffer())) Otherwise it could just be: fetch('../out/main.wasm').then(WebAssembly.instantiateStreaming)

Post by [deleted] » Wed, Apr 11, 2018, 11:20 PM UTC

dmix wrote: post #62

Promarged wrote: post #32

If available it's better to use instantiateStreaming [0] for faster compilation, e.g. this: fetch('../out/main.wasm').then(response => response.arrayBuffer() ).then(bytes => WebAssembly.instantiate(bytes)) could be expressed as this: fetch('../out/main.wasm').then(response => WebAssembly.instantiateStreaming(response)) [0]: https://hacks.mozilla.org/2018/01/making-webassembly-even-fa...

Wouldn't that still require `response.arrayBuffer()`? For ex (line 2): fetch('../out/main.wasm').then(response => WebAssembly.instantiateStreaming(response.arrayBuffer())) Otherwise it could just be: fetch('../out/main.wasm').then(WebAssembly.instantiateStreaming)

Post by kristianp » Thu, Apr 12, 2018, 12:00 AM UTC

puzzle wrote: post #56

pjmlp wrote: post #36

Earlier quoted context omitted.

Then you need to improve your Google-fu. Burroughs, Xerox PARC systems, ETHZ Lilith, Pascal UCSD, IBM TIMI, IBM Language Environment, ...

Also Oberon SDE...