miniquad VS arewegameyet

You also have Miniquad which is a very cool minimal graphics project. It has almost zero dependencies (only system ones), and compiles under 2 seconds to give you a window with OpenGL on all platforms including mobile very easily. It has a wrapper graphics API but it doesn't try to be modeled after OpenGL at all (after all it might support Metal in the future), so it's gonna be quite different doing your project in it, but it's still the same kind of low level graphics.

Theirs also https://github.com/asny/three-d or https://github.com/not-fl3/miniquad. Or lower level ones like WGPU or GLOW.

In that same rust game jam the second most used engine was macroquad, which was used by 3 games, two of which are playable in the browser. Macroquad is a cross-platform game library inspired by raylib. Macroquad is built on top of miniquad. I think macroquad is a bit more approachable than bevy since macroquad doesn't impose an ECS and tries to be minimal with its features so they are available in all of the platforms it targets.

(miniquad is a lower level lib https://github.com/not-fl3/miniquad - both miniquad and good-web-game is built on top of it)

Nice! Would love to see the same thing done with miniquad though.

Looks like it won't work out of the box, unfortunately, since {macro,mini}quad doesn't support a custom X11 parent window :-(

But I've opened an issue upstream to track functionality in the renderer that would allow this[1].

[1]: https://github.com/not-fl3/miniquad/issues/250

Single command deploy for both WASM and Android build instructions

Hi, I am using macroquad. There is an issue with `window_reizable` property. In my archlinux, this property doesn't work when set to `false`. Then I saw here that it is used only for windows. If I am correct, could you let me know the reason for this? Thanks

If you want to write your own shaders: miniquad.

arewegameyet

"While the ecosystem is still very young, you can find enough libraries and game engines to sink your teeth into doing some slightly experimental gamedev."

I think Rust for games has come really far. I will cite https://arewegameyet.rs/ "Almost. We have the blocks, bring your own glue.".

All the blocks are there and the language is really well suited to games.

On top of my head:

The pros:

- The crate ecosystem and the package manager makes it really easy to integrate any useful component such as pathfinding, spatial partitioning, graphics backend, audio system.. Most crates take a lot of effort to be cross-platform so I can develop on linux and not spend too much time debugging windows releases.

- The strong typing and algebraic data types makes expressing the game state very pleasant. I also found I was able to develop a very big game without too many bugs even though I don't write many tests.

- Ahead of time compilation + LLVM guarantees you won't have to optimise for weird things around a virtual machine. Rust gives you more control to optimise hot loops as you can go low-level.

- I find wgpu to be the perfect balance between ergonomics and power compared to Vulkan. OpenGL support through wgpu is also a nice addition for lower end devices.

- The Rust community is very helpful, you can often talk directly to crate maintainers

The cons:

- Compilation times, when compared to JITed languages such as C# can be very painful. It can be alleviated by buying a 3950X but I still often get 10-30s iteration times.

- The static nature of Rust means you often need a dynamism layer above to tweak stuff that can be awkward to manage. I made inline_tweak for this purpose but it's really far from how easy Unity makes it. https://github.com/Uriopass/inline_tweak

- Since Rust feels very ergonomic, you are tempted to write almost all game logic within it, so mod support feels very backwards to implement as you cannot really tweak "everything" like in Unity games. Thankfully "Systems" game like Factorio or Egregoria can be theoretically split into the "simulation" and the "entities" so mod can still have a great impact. Factorio is built in C++ so has the same problematic. Their Lua API surface is quite insane to be able to hook into everything. https://lua-api.factorio.com/latest/

Now, I have to talk about Bevy: https://bevyengine.org/. It did not exist when I started but it is a revolution in the Rust gamedev space. It is a very powerful 100% Rust game engine that makes you write game code in Rust too. It has incredible energy behind it and I feel like if I'd used Bevy from the start I wouldn't have had to develop many core engine systems. Its modular design is also incredibly pleasant as you can just replace any part you don't like with your own.

For practical uses of Rust? Whatever you want to program. People use Rust for game development, GUIs, web dev, and more. Anything where abstraction, speed, concurrency, memory safety, etc. are important, Rust will probably be a good fit.

Are we game yet? "Almost. We have the blocks, bring your own glue"

Not seeing anything else that's close to photo realistic. I'm hitting the tough bugs first all too often. More than half my time has been spent on ecosystem problems.

I also know of https://arewegameyet.rs/

Yes — and in fact, Firefox's implementation has been the go-to graphics API for folks trying to make Rust gamedev happen for a long time now. Bevy Engine's renderer is built on it, for example.

They're all/mostly websites about the state of the Rust language ecosystem. For example, can you write games in Rust (https://arewegameyet.rs/) or what's the state of the async (https://areweasyncyet.rs/)