I have not dug into WASM myself. But, I've heard there are multiple implementations out there that are very nicely embeddable. They might well be good competition for Lua. I guess I'd ask a few different questions. Who is your target audience? Are they professional coders or semi-technical users? Are they in-house or are the customers in the wild?
If you have in-house coders who can't agree on what language to use, I guess WASM could allow them to agree to disagree. I'm not sure if that's a better path than using the languages' native tools and focusing on improving the compile-debug iteration time.
If you have external coder customers who will demand differing languages, WASM sounds great!
If you have external, semi-technical users who don't flat-out demand JavaScript-or-Die, standardizing on either Lua or Python is probably better for them both in terms of complexity and consistency of documentation and community help.
In general, for semi-technical users, see my above post on power levels.
If you have in-house coders who can't agree on what language to use, I guess WASM could allow them to agree to disagree. I'm not sure if that's a better path than using the languages' native tools and focusing on improving the compile-debug iteration time.
If you have external coder customers who will demand differing languages, WASM sounds great!
If you have external, semi-technical users who don't flat-out demand JavaScript-or-Die, standardizing on either Lua or Python is probably better for them both in terms of complexity and consistency of documentation and community help.
In general, for semi-technical users, see my above post on power levels.