Hacker News new | past | comments | ask | show | jobs | submit login

One thing I am concerned about is startup performance. On my (slow) Chromebook, some of my multi-megabyte WASM files take 10 seconds to compile. Seems we need either faster CPU cores, faster code generation, or some kind of staged JIT compile -- though I guess the latter could be accomplished today with sufficiently clever tooling.



Chrome Canary contains Liftoff, which is about 8x faster on my machine for initial compilation of wasm. I'm assuming it'll be in Chrome 69.


Indeed. X64 and ia32 support vor Liftoff will be in 69.


Wasm is set up to be able to do streaming compilation, I wonder if that helps at all? It's in a least Chrome and Firefox...


Think about if the same codebase were in JS, it would definitely be slower. But like others are saying, streaming is one of the main features of wasm.




Consider applying for YC's Summer 2025 batch! Applications are open till May 13

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: