Re:Wasmer 5.0
by mike_r_parsons on Wednesday October 30, 2024 @04:37AM
(#41992947)
I really don't know what problem(s) this solves. Don't all the javascript runtimes already have wasm engines built into the runtimes?
[ Parent
| on HN ]
You don't need to carry around a whole Javascript engine when all you want is running some WASM/WASI code. Granted, the real-world differences aren't all that big:
- wasmer: single 45 MByte exe
- wasmtime: single 28 MByte exe
- node.js: 87 MByte, lots of individual files
- deno: 186 MByte over two executables (deno and denort not sure what denort is though)
As an extreme outlier, there's wasm3 which is a WASI interpreter and which is just a single 255 KB executable (not a typo).All sizes looked up on an ARM Mac.
Re:Wasmer 5.0
by mike_r_parsons on Thursday October 31, 2024 @03:50AM
(#42004360)
Is this (size) an issue in the real world?
It depends what real world is for you. In embedded or with low bandwith it might.