+++ title = "This Month in Rust GameDev #11 - June 2020" date = 2020-07-01 transparent = true draft = true +++
Welcome to the eleventh issue of the Rust GameDev Workgroup’s monthly newsletter. Rust is a systems language pursuing the trifecta: safety, concurrency, and speed. These goals are well-aligned with game development. We hope to build an inviting ecosystem for anyone wishing to use Rust in their development process! Want to get involved? Join the Rust GameDev working group!
You can follow the newsletter creation process by watching the coordination issues. Want something mentioned in the next newsletter? Send us a pull request. Feel free to send PRs about your own projects!
Table of contents:
- Game Updates
- Learning Material Updates
- Library & Tooling Updates
- Popular Workgroup Issues in Github
- Meeting Minutes
- Requests for Contribution
- Jobs
- Bonus
yaks is a minimalistic framework for automatic multithreading
of hecs
ECS library using Rayon data-parallelism library.
While the project itself started earlier this year, with this month's release
yaks
gained an overhauled API, further leaning into the promise of
simplicity:
- systems are any functions or closures of a specific signature,
Executor
is a container for one or more systems,- system execution order can be defined when building an
Executor
to create concurrent chains of systems, - resources used by systems (any data that is not associated with an entity) are now borrowed for the duration of execution, instead of being owned by the framework.
All items in the library are exhaustively documented, and the repository contains a fully annotated example.
Enabled-by-default parallel
cargo feature can be disabled to force
everything in yaks
to become single-threaded, which allows using code
written with the framework on platforms without threading - notably, web.
See all meeting issues including full text notes or join the next meeting.
- Embark's open issues (embark.rs);
- winit's "Good first issue" and “help wanted” issues;
- gfx-rs's "contributor-friendly" issues;
- wgpu's "help wanted" issues;
- luminance's "low hanging fruit" issues;
- ggez's "good first issue" issues;
- Veloren's "beginner" issues;
- Amethyst's "good first issue" issues;
- A/B Street's "good first issue" issues;
- Mun's "good first issue" issues;
Just an interesting Rust gamedev link from the past. :)
That's all news for today, thanks for reading!
Subscribe to @rust_gamedev on Twitter or /r/rust_gamedev subreddit if you want to receive fresh news!