3 ms·

So Clang itself was compiled to WebAssembly? That's slick, even if it does take forever to load.

by mark-r 9y ago

ateesdalejr 9y ago
2mins or so. Not bad.
- mark-r 9y ago
  2 minutes is truly forever on the web. I found myself wondering if there was something wrong with the page.
- okket 9y ago
  ~20 sec in my Late 2013 MBP from page load to "The [cake] is a lie," in Chrome 63. Sadly it does not work in Safari or Safari Tech Preview, but it works in Firefox 57 (known problem, see https://github.com/tbfleming/cib https://github.com/tbfleming/cib)
jmgao 9y ago
clang is pretty big. There's about 55 MB of binaries on that page. When served from localhost, it takes about 10 seconds to load and compile a source file on my machine.
- solarkraft 9y ago
  This gets us to two caching-related problems: What if you're offline and how do you decide what you want to be cached? But browser vendors will solve this.
  - imtringued 9y ago
    Isn't this solved with progressive web apps? On the other hand I'm not aware of any UI that allows you to explicitly choose if a PWA should be cached or not.
sitkack 9y ago
What about packing up web assembly into a single file container like runtime designed to run server side web applications? This .war (Webassembly ARchive) file could include the application and all dependencies in a single installable that is JITd on load. Might be useful for the next generation of "serverless" cloud runtimes.
- dpratt 9y ago
  I see what you did there. I’d be all for this, honestly, except that the existing containers (yes, even Jetty) are too heavyweight for this use case. What you really want is a stripped down server runtime that loads and starts your application’s archive, fires it up on a (possibly random) local port and opens a stripped down Chromium instance that loads the app from that port. Of course, that sounds a bit like Electron.
  - imtringued 9y ago
    Node.js supports webassembly.
- solarkraft 9y ago
  This will probably happen. Hopefully properly compatibly.
- tzahola 9y ago
  >.war (Webassembly ARchive) This is sarcasm, right? If it is, it's damn good.

So Clang itself was compiled to WebAssembly? That's slick, even if it does take forever to load.

by mark-r 9y ago

So Clang itself was compiled to WebAssembly? That's slick, even if it does take forever to load.

ateesdalejr 9y ago

2mins or so. Not bad.

mark-r 9y ago
2 minutes is truly forever on the web. I found myself wondering if there was something wrong with the page.
okket 9y ago
~20 sec in my Late 2013 MBP from page load to "The [cake] is a lie," in Chrome 63. Sadly it does not work in Safari or Safari Tech Preview, but it works in Firefox 57 (known problem, see https://github.com/tbfleming/cib https://github.com/tbfleming/cib)

jmgao 9y ago

clang is pretty big. There's about 55 MB of binaries on that page. When served from localhost, it takes about 10 seconds to load and compile a source file on my machine.

solarkraft 9y ago
This gets us to two caching-related problems: What if you're offline and how do you decide what you want to be cached? But browser vendors will solve this.
- imtringued 9y ago
  Isn't this solved with progressive web apps? On the other hand I'm not aware of any UI that allows you to explicitly choose if a PWA should be cached or not.

sitkack 9y ago

What about packing up web assembly into a single file container like runtime designed to run server side web applications? This .war (Webassembly ARchive) file could include the application and all dependencies in a single installable that is JITd on load. Might be useful for the next generation of "serverless" cloud runtimes.

dpratt 9y ago
I see what you did there. I’d be all for this, honestly, except that the existing containers (yes, even Jetty) are too heavyweight for this use case. What you really want is a stripped down server runtime that loads and starts your application’s archive, fires it up on a (possibly random) local port and opens a stripped down Chromium instance that loads the app from that port. Of course, that sounds a bit like Electron.
- imtringued 9y ago
  Node.js supports webassembly.
solarkraft 9y ago
This will probably happen. Hopefully properly compatibly.
tzahola 9y ago
>.war (Webassembly ARchive) This is sarcasm, right? If it is, it's damn good.