libCat VS arewegameyet

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!

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.

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.

I use clang-tidy. These are my current linting rules.

I'm working on this! https://github.com/Cons-Cat/LibCat

For practical uses of Rust? Whatever you want to program. People use Rust for game development, GUIs, web dev, and more. Anything where abstraction, speed, concurrency, memory safety, etc. are important, Rust will probably be a good fit.

Are we game yet? "Almost. We have the blocks, bring your own glue"

Not seeing anything else that's close to photo realistic. I'm hitting the tough bugs first all too often. More than half my time has been spent on ecosystem problems.

I also know of https://arewegameyet.rs/

Yes — and in fact, Firefox's implementation has been the go-to graphics API for folks trying to make Rust gamedev happen for a long time now. Bevy Engine's renderer is built on it, for example.

They're all/mostly websites about the state of the Rust language ecosystem. For example, can you write games in Rust (https://arewegameyet.rs/) or what's the state of the async (https://areweasyncyet.rs/)

Now comes the most controversial part of my answer: learn Rust. I cannot convey in works how insanely unfriendly the C/C++ world is to inexperienced programmers. This may sound counterintuitive, because the same can be said about Rust, but not really. It's much easier to get started with Rust and finish your first project than it is to learn how to manage, build, and maintain even the smallest of C++ projects. But this isn't why I'm asking you to migrate to rustland. My reason for suggesting so is WebGPU. WebGPU is probably the best modern graphics API that's also incredibly well-documented and beginner-friendly. For this reason I believe it to be the #1 API for beginners going forward. Rust has an increasingly great WebGPU story and graphics ecosystem. If this doesn't convince you, that's also ok. There's a beginner-friendly wrapper course for the Vulkan tutorial that you're following so you can go on with your Vulkan journey after you've done some exploring. Note that this course is incomplete and kinda in the middle of a hiatus, but what's there is more than enough to get you started.

rust-learning (A broader listing that includes links to sites like Are we game yet? among other things)

There's also the Scripting Languages section of Are we game yet?, though I'm not sure which of those are suitable for restricted execution.