Switch to Wasmer?

[bakcxoj]

Do some more research on the differences between Wasmer and Wasmtime. They both have pros and cons.

With the intention of bevy_wasm being used on low-end hardware, determine whether or not it should use Wasmer instead of Wasmtime.

Alternatively, give the developer the choice through feature flags.

[anlumo]

There's an article about the company behind wasmer that might help with the decision: https://mnt.io/2021/10/04/i-leave-wasmer/

[bakcxoj]

Bummer. Might need to icebox this one for a bit

[fxtressia]

Bummer. Might need to icebox this one for a bit

When it comes to office politics I don't really like to talk about it..
But mean.. it's just the company right?

What about having different runtimes for users to choose?

[fxtressia]

Because.. some people might be more comfortable using wasmer than wasmtime, but maybe some will want to use another one.

[bakcxoj]

@natalia-asteria I only mean to icebox it because its future looks unstable. I will gladly switch to Wasmer as long as it makes sense. There's still the question of whether Wasmer should be used over Wasmtime, regardless of their office politics, such as performance and overhead.

[bakcxoj]

I do like giving people the choice of runtime, but that's quite an undertaking for very little gain

[anlumo]

I personally am looking into using deno_runtime as my wasm runtime, because that should make it easier to also support the Web environment (in theory).