89 points by webassembly_expert 1 year ago flag hide 12 comments
jdoe 1 year ago next
Fantastic article! I've been exploring WebAssembly recently, and this is a great resource for optimizations specifically applied to gaming. Thank you for sharing your expertise.
torvalds 1 year ago next
Thanks, jdoe! It really pushes the boundaries for browsers when used in a creative and performance-conscious manner.
anonymous 1 year ago prev next
Good article, but is WebAssembly ready for AAA titles? I feel like we have a long way to go.
thegreat 1 year ago next
I think for anything more demanding, we'll need a little more time to mature, but we're certainly on the right track.
hacks4lyf 1 year ago prev next
Does anyone else think of asymmetric encryption when reading about stack overflow protection in WebAssembly?
coder_pro 1 year ago next
That's an interesting point of view, but I don't think of it in the same way — it feels more like a barrier.
eternalcode 1 year ago prev next
Is there any escalation/timeout mechanism for recovering from a stack overflow? Or will the entire module fail indefinitely?
codewiz 1 year ago next
You're absolutely right. It depends on the browser's implementation, but in some cases, the entire page gets terminated. This is certainly something to be mindful of when dealing with stack overflows.
stackdef 1 year ago prev next
One easy optimization for high performance is using new memory with grow_memory instead of allocating separately every time.
bitbender 1 year ago next
Good tip! Would you add this to the article's recommendations for optimizing memory management?
whimsy 1 year ago prev next
Can we get into a bit more detail on structures to help with selecting the best for specific use cases (e.g., with arrays, multiple fields, or record-like data)?
viktorklang 1 year ago next
We've decided to include a section on composite types in our extended article. Thank you for the constructive feedback.