3 ms·

Well, wasm runs slower right? I'm not that familiar. Seems that if wasm is a goal, then that might negate they did this for performance. What other benefit

Well, wasm runs slower right? I'm not that familiar. Seems that if wasm is a goal, then that might negate they did this for performance. What other benefit is there to wasm that would make it a fit for Q#?

hu3 3y ago
Slower than native perhaps. But usually faster than JavaScript on V8. So if you want fast browser perf, Wasm is a great choice. There's also Wasm on the edge with the likes of Cloudflare Workers and Vercel https://vercel.com/docs/concepts/functions/edge-functions/wasm https://vercel.com/docs/concepts/functions/edge-functions/wa... It also has some interesting isolation properties.
- syrusakbary 3y ago
  Shameless plug for WebAssembly on the Edge: Wasmer recently launched Wasmer Edge, which is Wasm-focused instead of JS-focused compared to Cloudflare Workers and Vercel https://wasmer.io/products/edge https://wasmer.io/products/edge
  - hu3 3y ago
    I respect the hustle. Sorry for not mentioning https://wasmer.io https://wasmer.io. Keep it up! Competition is great.
  - kentonv 3y ago
    When this site says Wasmer's "cold start time" is 50ns, what is it measuring? You can't even do a syscall in 50ns. Cloudflare's 5ms includes time to read the application code from disk. (I'm the one who originally did this measurement.)
    - syrusakbary 3y ago
      Hi Kenton! 50ns is the median time to initialize the Wasm module. I think it would make sense to do another round of measuring with more factors that test things end to end, and see how each of the platform performs. BTW, I'm a big admirer of Cloudflare Workers... great work!