awesome-ebitengine VS wazero

Hey, author here. I am glad to answer any questions.

Ebitengine is a blast to use as a game developer, and if you are at all considering trying it out, please do. The awesome-ebitengine repository links out to a lot of helpful developer resources:

https://github.com/sedyh/awesome-ebitengine

I have been a happy user of Ebitengine for several years. If you are interested in seeing the source of some games created with it, check out the awesome-ebitengine list.

https://github.com/sedyh/awesome-ebitengine

All of the games listed on my itch.io profile were created using Ebitengine, and they are all open source.

https://rocketnine.itch.io

This is a list of released, open source games created in Go using the Ebitengine game engine:

https://github.com/sedyh/awesome-ebitengine#games

Also here is a list of gamedev libs for Golang. Most are engine agnostic: https://github.com/sedyh/awesome-ebitengine

Awesome Ebitengine

There’s a graphics library https://github.com/hajimehoshi/ebiten that is fairly popular. Someone has a list of projects using it https://github.com/sedyh/awesome-ebiten

Awesome Ebiten, an index of useful resources for anyone interested in Ebiten.

https://github.com/tetratelabs/wazero/releases/tag/v1.7.0

This includes the final release of the new optimizing compiler, which is a big improvement over the previous one.

The new version also adds experimental support for threads and snapshot/restore (setjmp/longjmp).

This is already being used by go-pgquery, all will mean that sqlc won't need to ship to almost copies of wazero (these features had been implemented on a friendly fork, and have now been up-streamed).

> Go actually has one of the best WASM runtimes https://github.com/tetratelabs/wazero

Wazero looks super cool. I saw somewhere that programs can be run with a timeout, which sounds great for sandboxing. The program input is just a slice of bytes [1], so an interesting use case would be to use something like Nats [2] to distribute programs to different servers. Super simple distributed computing!

--

1: https://github.com/tetratelabs/wazero/blob/main/examples/bas...

2: https://natsbyexample.com/examples/messaging/pub-sub/go

It is slower.

The WASM runtime wazero [1] uses a compiler on amd64 and arm64 (on Linux, macOS, Windows, and FreeBSD), but the current compiler is very fast (at compiling), but very naive (generates less than optimal code).

An optimizing compiler is currently being developed, and should be released in the coming months. I'm optimistic that this compiler will cover the performance gap between WASM and modernc.

[1]: https://wazero.io

I am a fan of the Jacobin project! For your uses, you may also want to consider wazero [1], a pure-go WebAssembly runtime. Full disclosure: I am on the team :)

[1]: https://wazero.io/

No longer does Wasm/WASI need JS host! There are many spec-compliant runtimes built for environments from tiny embedded systems up to beefy arm/x86 racks:

- https://github.com/bytecodealliance/wasm-micro-runtime

- https://github.com/bytecodealliance/wasmtime

- https://github.com/wasmerio/wasmer

- https://github.com/tetratelabs/wazero

- https://github.com/extism/extism (disclaimer, my company's project - makes wasm easily embeddable into 16+ programming languages!)

full disclosure: I don't work on it, but the devs are committers/contributors to https://wazero.io (I am a wazero committer) :)