3 ms·

btw. for what it's worth their javascript to wasm is opensource: - https://github.com/fastly/js-compute-runtime https://github.com/fastly/js-compute-runtime -

by merb 5y ago

btw. for what it's worth their javascript to wasm is opensource: - https://github.com/fastly/js-compute-runtime https://github.com/fastly/js-compute-runtime - https://github.com/tschneidereit/spidermonkey-wasi-embedding https://github.com/tschneidereit/spidermonkey-wasi-embedding and besides that it is slower than nodejs it is still plenty fast (no matter that it is not as fast as they want) btw. it's startup is faster than node. (maybe better pgo might help) its insane what they built, to do it and it will bring the whole wasm community forward if they succeed (and I hope they do)

NicoJuicy 5y ago
Gentle reminder: That's mostly because they acquired the team behind wasm. Which was already an opensource project at Mozilla. Post on HN: https://news.ycombinator.com/item?id=24897641 https://news.ycombinator.com/item?id=24897641
- tschneidereit 5y ago
  It's really the other way around: we joined Fastly because we knew it's a place where we could do this kind of work in the open. None of the code involved here existed a year ago, and none of it was somehow forced to be open source. (Also, the code in these two repositories is in many ways the most boring part of this solution. See this blog post for an excellent overview of the more interesting parts: https://bytecodealliance.org/articles/making-javascript-run-fast-on-webassembly https://bytecodealliance.org/articles/making-javascript-run-...)
  - NicoJuicy 5y ago
    The article I linked too ( and the hn comments) in my original post seemed that fastly acquired the wasm team. Sorry if I was mistaking.
    - tschneidereit 5y ago
      Oh, no worries at all! While there was no acquisition involved, a whole group of folks working on WebAssembly at Mozilla (myself included) moved to Fastly last Fall. What I tried to emphasize is that instead of the projects at hand here being open source because they somehow had to be, we all joined Fastly because it's a place where this kind of project can be made open source (and be created in the first place!) :)

by merb 5y ago

NicoJuicy 5y ago

Gentle reminder: That's mostly because they acquired the team behind wasm. Which was already an opensource project at Mozilla. Post on HN: https://news.ycombinator.com/item?id=24897641 https://news.ycombinator.com/item?id=24897641

tschneidereit 5y ago
It's really the other way around: we joined Fastly because we knew it's a place where we could do this kind of work in the open. None of the code involved here existed a year ago, and none of it was somehow forced to be open source. (Also, the code in these two repositories is in many ways the most boring part of this solution. See this blog post for an excellent overview of the more interesting parts: https://bytecodealliance.org/articles/making-javascript-run-fast-on-webassembly https://bytecodealliance.org/articles/making-javascript-run-...)
- NicoJuicy 5y ago
  The article I linked too ( and the hn comments) in my original post seemed that fastly acquired the wasm team. Sorry if I was mistaking.
  - tschneidereit 5y ago
    Oh, no worries at all! While there was no acquisition involved, a whole group of folks working on WebAssembly at Mozilla (myself included) moved to Fastly last Fall. What I tried to emphasize is that instead of the projects at hand here being open source because they somehow had to be, we all joined Fastly because it's a place where this kind of project can be made open source (and be created in the first place!) :)