3 ms·
> This is why I'm optimistic about WebAssembly, beyond time and investment, what prohibits it from achieve performance parity with native? It's cross-platform
by handrous 5y ago
> This is why I'm optimistic about WebAssembly, beyond time and investment, what prohibits it from achieve performance parity with native?
It's cross-platform VM-enabled bytecode? Approaching native performance very closely is the best plausible outcome. Measured on all metrics and not just pure number-crunching (start-up time generally, "cold" start-up, memory use, memory use over time, et c., all in real-world applications and not bespoke benchmarking programs) it's unlikely it'll even get very close. Close enough? Maybe, but I'm skeptical that there is such a (realistic) achievable state as "close enough" on a platform that runs on a small battery. Look at Android's decades of playing catch-up on performance & power use, for instance.
[EDIT] Down-voters, please comment: do first-year CS principles and direct observation of existing, long-lived, real-world cross-platform VM systems (the JVM, for example) somehow not apply to WebAssembly?