libCat VS blender-tools

That's awesome! I'm working on something that sounds similar. https://github.com/cons-cat/libcat

I'd love to see your work if you're willing to share it here!

This runtime size bothers me a lot. So much that I've been working on a new runtime for C++ that breaks POSIX compatibility to keep binaries as small as they can be. The hello world with LTO is 330ish bytes right now, and I think that can get smaller. https://github.com/Cons-Cat/libCat

I'm working on a library that replaces both C++ and C/POSIX standard libraries (https://github.com/Cons-Cat/libCat), but even then I need to define a few std:: namespace symbols for some features. In the case of std::initializer_list, my answer is just don't use that feature, because you don't really need it.

It's worse in the standard library than it has to be. When I refactored my traits to minimize template instantiations and lean on concepts as much as possible, I measured over 30% improvement to clean build compile times. It's not possible for the standard to do this, because it would subtly change the API. For instance, you can't instantiate or take the address of a concept, but you can for a type-trait class. No reason you'd want to do that, but you can, so they can't "break" the standard library by optimizing this.

This doesn't have to be true. Over the past year I've made progress towards demonstrating how even non-freestanding C++ can be written without any C or C++ standard library headers or DLLs (with large benefits). There are a few names which the compilers require to be in the std:: namespace, though, but they're very special features like source_location and construct_at with semantics that can't be expressed otherwise.

This bit cast has no overhead in debug mode, and is a little bit more generally useful than std::bit_cast(), but cannot be constant evaluated. https://github.com/Cons-Cat/libCat/blob/main/src/libraries/utility/implementations/bit_cast.tpp

It isn't that hard to put a predicate into a type. We have lambdas in an unevaluated context, CTAD, and templated type aliases. https://github.com/Cons-Cat/libCat/blob/main/src/libraries/scaredy/cat/scaredy https://github.com/Cons-Cat/libCat/blob/main/src/global_includes.hpp#L70 https://github.com/Cons-Cat/libCat/blob/main/src/libraries/linux/cat/linux#L289 You do it like this.

But suppose that you have code with no standard library calls at all. Would it still make sense to choose this naming convention? This is actually possible, with a few special exceptions. GCC requires that an implementation of std::source_location has very particular class member names, GCC assigns special semantics to a few function names including std::construct_at and std::move (people seem to know it's inlined, but did you know std::move is required for move-related warnings?), and most intrusively of all, a promise_type must be snake_case. Other names can be worked around by using them into a different namespace with a different letter-case, but promise_type seems unavoidable.

I use C++ for a low-level Linux runtime. Other people are using it for operating systems like SerenityOS and Zircon/Fuschia. People also use C++ for making more compilers like GCC and LLVM.

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