blender-tools VS winsafe

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 know all that shit because I'm the author of Rust's WinSafe library, which is a safer Rust layer over native Win32, so I had to deal with a lot of shit like this.

[dependencies] winsafe = { git = "https://github.com/rodrigocfd/winsafe", features = ["kernel"] }

Externally, you can write a lot of native Windows stuff in Rust already. Personally, I'm having a lot of fun with WinSafe.

If you had such problems (which I also had in the past), I'm really interested in you opinion about WinSafe, and if it could help you solving them.

If you're after a native Windows application, WinSafe may suit your needs.

As the author of WinSafe, I can say it's tedious sometimes, but it's often very challenging, because you have to translate crazy unsafe behaviors into Rust's ownership model. It's surely hard, but also very rewarding at the end.

As the author of the WinSafe lib, I wholeheartedly agree.

I don't know how rare this is (or how rare it should be), but this issue warned me about this potential problem, and I had to make a huge refactoring to treat the possibility. I had to rethink many aspects of all handle implementations. It was hard work, but in the end it was worth it.

WinSafe says hello.

WinSafe, for example (which attemps to be a safe layer over the Windows API), provides lots of RAII automations. A fine example is the BeginPaint function: