blender-tools VS wise_enum

I work at Embark Studios on our creative platform. Our team is building everything in rust.

Tons of big companies are using it: Amazon, Discord, Cloudflare, etc. You can read about their success stories. As for game development, Veloren is a pretty complex game, and it's written entirely in Rust. Embark is betting on Rust for their game dev projects. ECS makes the dream work here, but an Actor framework would work too. You don't need DI. For example, in the web services I write using Actix, application state (stuff like clients for redis or http, db connection pool, etc.) is stored globally, and shared through the application state extractor. No dependency injection, but accessing that global state is just as convenient as if it was DI. If it's shared across workers, you put it behind a mutex/rwlock or use a concurrent data structure.

https://embark.dev/ is a major player in the rust ecosystem right now. They look like they are aiming for more of a startup feel rather than an indie one.

We are at Embark! https://embark.dev/, https://embark.rs, https://embark.games.

Is a remote-first culture, Rust-only team building our game platform from scratch on all levels and all types of code (gameplay, engine, generalists, backend, research/ml), and with a strong focus on open source.

Tons of game studios are using Blender in production. And for environment creation 3dsMax is much more popular in games. 2 Blender examples: - Embark: https://github.com/EmbarkStudios/blender-tools - Ubisoft: https://github.com/ubisoft/mixer

I can't keep up! First we have better enum, then some guy at a conference says we have to use wise enum instead, and now you speak of magic enum!

There are already several working, well-known and used hacks mechanisms available to reflect on enums. For example, magic enum, wise enum, Boost.Describe, and so on.