aoc2021 | macroquad | |
---|---|---|
1 | 56 | |
0 | 2,844 | |
- | - | |
10.0 | 7.8 | |
over 2 years ago | 1 day ago | |
Rust | Rust | |
- | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
aoc2021
-
C++'s smaller cleaner language
For instance, maybe I'm just overestimating how verbose C++ would have been, or maybe I managed a particularly concise Rust AOC, but my solutions haven't been bad at all. See last year's, with no dependencies outside the standard library: https://github.com/rpjohnst/aoc2021/tree/main/src/bin
macroquad
-
Deploying your Rust WASM Game to Web with Shuttle & Axum
See the macroquad docs for full details on building a WASM game.
- Not only Unity...
- Macroquad: Cross-platform game engine in Rust
-
What would you recommend for simple 2D game (in The Binding of Isaac style)?
Any opinion on ggez? I don't like how everything in macroquad is global state https://github.com/not-fl3/macroquad/issues/333
-
Help with egui basics?
I prefer examples like the ones in Macroquad: https://github.com/not-fl3/macroquad/tree/master/examples. I'm not against advanced examples, but the priority should be extremely clear, minimal, self contained ones.
-
HELP: Unique ID's starting at 0 for each Type, advancing by one.
There were even discussions about deprecating static mut. Even if you think you got it right, there are too many things that might go wrong, like aliasing. For example, macroquad needs a complete rewrite because of their static mut.
-
Learning project - board game Yinsh using macroquad
It's based on macroquad and you can play the wasm version here: https://unvirtual.github.io/yinsh-rs/
-
I love rust, I have a pet peeve with the community
The reality is that I have used unsafe that is also unsound out of convenience because fixing it is a papercut too many. And this tends to be common! I know enough to spot unsoundness in other projects (sometimes even early). But not enough to be confident in my own abilities to write sound unsafe code. Why? Because it's really flipping hard, that's why!
-
Limitations of wasm for a small board game?
Given that you are making a game, you might want to consider using a game framework such as https://github.com/not-fl3/macroquad/.Macroquad has full support for WASM, and will allow you to render your game both locally and in the browser via WASM depending on how you compile it.
What are some alternatives?
eve - Expressive Vector Engine - SIMD in C++ Goes Brrrr
miniquad - Cross platform rendering in Rust
pacman - A proof that Idris is pacman complete
bevy - A refreshingly simple data-driven game engine built in Rust
mp-units - The quantities and units library for C++
ggez - Rust library to create a Good Game Easily
libCat - 🐈⬛ A runtime for C++26 w/out libC or POSIX. Smaller binaries, only arena allocators, SIMD, stronger type safety than STL, and value-based errors!
pixels - A tiny hardware-accelerated pixel frame buffer. 🦀
cppfront - A personal experimental C++ Syntax 2 -> Syntax 1 compiler
raylib - A simple and easy-to-use library to enjoy videogames programming
dmd - dmd D Programming Language compiler
gdnative - Rust bindings for Godot 3