assemblyscript VS mlua

Incidentally, it’s also what AssemblyScript uses: https://github.com/AssemblyScript/assemblyscript/blob/main/s...

Use it as a Front-End for other low-level languages.

> MHO typescript could just cut loose from its javascript compatibility. Why not compile it to wasm instead of transpiling it to javascript?

Check out AssemblyScript which is exactly that:

https://www.assemblyscript.org/

If you're curious, check out AssemblyScript, that might describe better what needs to be cut from TypeScript to make it possible to be compiled to WASM.

This is kinda the idea behind AssemblyScript, but IIRC it's more of a low-level typescript-ish syntax for WebAssembly.

https://www.assemblyscript.org/ maybe, but I'm not sure exactly what you need.

Exactly, WASM was designed to be very very lightweight... you can put a lot of logic into a very small amount of WASM, but you need a good compiler to do that, or write WASM by hand to really feel the benefit. If you just compile Go to WASM, with its GC, runtime and stdlib included in the binary, yeah it's going to be pretty heavy... Rust doesn't have a runtime but as you said, for some reason, produces relatively large binaries (not the case only in WASM by the way). Probably, the best ways to create small WASM binaries is to compile from C or from a WASM-native language like AssemblySCript (https://www.assemblyscript.org).

Well we have all the new ECMA standards that will be introduced in 5 years now. It's looking more like Java actually. its accessor and typing patterns match it the most. TypeScript has had quite the profound influence over future ECMA design. There is a not so well known project called AssemblyScript which I think has a promising future. Since future ecma standards closely resembles it and TypeScripts popularity has exploded I have a feeling it may become a real standard as well.

If you can guarantee that Typescript type hints will always be followed, you can turn it into more optimised code. Unfortunately, this means you've got to break Javascript semantics, so this means creating a new language, but people have done it. For example, AssemblyScript is a language that is designed as a strict subset of Typescript that compiles directly down to WebAssembly instead of Javascript, producing much more efficient code (most of the time). The tradeoff is that it has some slightly different semantics to Javascript, which means your existing codebase — and most of the libraries you use — will probably require some adaption before running correctly in AssemblyScript.

The release notes can be found here.

I'm not a specialist about text based multiplayer game, but from what I saw on Wikipedia it seem doable to do it with Rust and Bevy. On top of that you can add a layer of LUA with https://github.com/khvzak/mlua (or write your own bindings and sandbox later).

mlua can run on emscripten target with Luau backend -> https://github.com/khvzak/mlua/issues/23

You can also look at the "dependents" section on crates.io https://crates.io/crates/mlua/reverse_dependencies and github https://github.com/khvzak/mlua/network/dependents

I know mlua does support Async. I also prefer it over rlua

Note rlua doesn't allow you to create native modules with it and has largely been superseded by https://github.com/khvzak/mlua since it's more maintained, has native module support and stuff like Luau and async/await.

I'm glad to announce first mlua version 0.8.0-beta.1 with Roblox Luau support.

I believe mlua [0] is the recommended Lua Rust binding now.

[0] https://github.com/khvzak/mlua

This is achieved through a backend/client architecture -- all core functionality (getting query results, opening selected item, search engine fallback, etc.) is implemented in a "backend" module, which is a Rust library exposed as a Lua module via mlua. The results returned by the backend then get fed into your fuzzy-finder of choice through thin clients, or "providers".