3 ms·

Hmm, not sure... Author's argument is "because it is easier today and will be as powerful as containers in the future". Well, what about it gets as powerful b

Hmm, not sure... Author's argument is "because it is easier today and will be as powerful as containers in the future". Well, what about it gets as powerful but 3 times more complex? Frankly, I find it quite messy to develop WASM in C++ without downloading an emscripten ...container. Yeah, AFAIK, there is no WASM compiler in WASM. Oh an there is the *in the browser*, also. Yeah, but the truth of the matter is that most WASM frameworks have a mediocre performance when compared to JS (because of the memory isolation). In this job we love new projects. We like them so much that we keep forgetting that the vast majority of them fail.

mdaniel 2y ago
> Yeah, AFAIK, there is no WASM compiler in WASM. What would you do with one if you had it? Run it on your wasm OS?
- diego_moita 2y ago
  You noticed this post is about WASM replacing containers, right? So, I'd use it the same way we use compilers in containers (i.e: one single download, no installation) and would run it with a runtime like Wasmer, Wasmtime, Wasmedge, etc. Or else I could run it sandboxed in a browser as a PWA. Then you could build things in Chromebook, phone, etc.
  - mdaniel 2y ago
    > Or else I could run it sandboxed in a browser as a PWA. $ du -hs $HOMEBREW_CELLAR/gcc/* 527M /usr/local/Cellar/gcc/14.2.0_1 (nod)