Our great sponsors
-
For this web-service I talked about, I needed graphql queries, I liked to have them statically typed and generated via a graphql-schema. For C# the only thing that could do it, I've found was https://chillicream.com/docs/strawberryshake for Rust there is https://github.com/graphql-rust/graphql-client I quickly ran into a bug in Strawberry Shake (exception), while with graphql-client although being a zero-ver never had an issue.
-
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.
-
SonarLint
Clean code begins in your IDE with SonarLint. Up your coding game and discover issues early. SonarLint is a free plugin that helps you find & fix bugs and security issues from the moment you start writing code. Install from your favorite IDE marketplace today.
-
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.
