Skip to content
Permalink
Branch: master
Find file Copy path
Find file Copy path
4 contributors

Users who have contributed to this file

@repi @arirawr @tshepang @Jake-Shadle
85 lines (48 sloc) 6.76 KB

Embark Rust Ecosystem

Embark logo

High-level tracking and discussions about improving Rust and the Rust ecosystem for our game development use cases at Embark.

Check out the Issues for active topics.

Background

When we started Embark, we chose Rust as our primary language for the long term future we are building. We love the safety and robustness of the language, the ability to write high performance, safe, and (mostly) bug free code and then fearlessly refactor and change it without common lifetime/ownership, memory safety or race condition problems.

That, combined with the openness and collaborative nature of the quickly growing ecosystem of and around Rust with crates.io and the tens of thousands of open source crates with a best-in-class package system, cargo, truly makes Rust a language for the next 40 years.

We believe that by openly sharing our work, issues, and ideas with the community, we'll create more opportunities for collaboration and discussion to bring us toward a great future for Rust and for the games industry in general.

-- Johan Andersson (@repi), CTO, Embark

Open Source

Open source Rust projects we've created so far and are actively using and maintaining:

Name Description Crates.io
πŸŒ‹ ash-molten Statically linked MoltenVK for Vulkan on Mac using Ash Latest version
πŸ‘· buildkite-jobify Kubekite, but in Rust, using configuration from your repos
❌ cargo-deny Cargo plugin to help you manage large dependency graphs Latest version
🎁 cargo-fetcher cargo fetch alternative for use in CI or other "clean" environments Latest version
🎳 physx-rs Use NVIDIA PhysX in Rust Latest version
🐏 rpmalloc-rs Cross-platform Rust global memory allocator using rpmalloc Latest version
πŸ†” spdx Helper crate for SPDX expressions. Latest version
πŸ“‚ tame-gcs Google Cloud Storage functions that follows the sans-io approach Latest version
πŸ” tame-oauth Small OAuth crate that follows the sans-io approach Latest version
🎨 texture-synthesis Example-based texture synthesis generator and CLI example Latest version

You can see all these crates on our crates.io profile.

Contributing

We encourage contributions to any of our open source projects. If you're not sure where to start, look at the GitHub issues on any of the above projects!

Check out guidelines.md for our guidelines & policies for how we develop in Rust.

To make sure we keep a friendly and safe environment for everyone, we have a Contributor Code of Conduct. You can read this in any of our projects' repositories. By contributing to our projects, you agree to the code of conduct.

Areas of Interest

Areas that we are interested in or working on, and want to help see improved in Rust:

  • ☸ Distributed systems - async, tokio, tower-grpc

  • πŸ•ΉοΈ Game engine systems - multiplayer, rendering, physics, audio, server, assets, workflows

  • πŸ“¦ Developer experience - fast iteration with large projects/monorepos, distributed builds, debugging, profiling, IDE

  • πŸ›Έ WebAssembly and WASI - sandboxed safe Rust code on client, edge & cloud

  • πŸ€– Machine learning - efficient inference, library bindings, training environments

  • πŸš€ High performance runtime - CPU job scheduling, code generation, optimizing crates

  • πŸ“ΊπŸ“± Console & mobile platform support - PlayStation, Xbox, future hw. iOS & Android. #18

  • 🏎 Rust on GPU - future compute & ML programming models beyond shaders

We track and discuss these from our perspective in the Issues for visibility and to get feedback, feel free to join in if you have ideas!

Also check out the Rust Game Development Working Group.

Sponsorships

We believe that open source creators are integral to the success of the Rust ecosystem. We offer monetary sponsorship to several individuals and projects via Patreon, GitHub and OpenCollective. You can see who we're currently supporting below:

Work with us!

We're actively looking to collaborate with developers on the areas discussed in this repository. If you're interested in working on a specific issue or idea highlighted here, please reach out to us at opensource@embark-studios.com to discuss contracting opportunities or sponsorship.

We are also hiring for full-time positions in Stockholm!

Let's go! πŸš€

You can’t perform that action at this time.