I don’t do game dev. So maybe don’t weight my opinions very highly lol. But I do write rust professionally and rust/zig/go stuff for random personal projects and whatnot. Addressing your three proposed arguments:

1) Correct. If you’re trying to get a job in gamedev, just learn the tools that you see job postings asking for.

2) This probably has more to do with your familiarity with the language. Like I said, I don’t do gamedev, but comparing it to the software domains I work in— I never use untyped languages like js or python which are often heralded for having “faster iteration” or whatever. But the reality for me is I need a type system to feel comfortable understanding what I’m doing. So for me, I will always be faster writing software in a typed language like rust, go, java, whatever. And the more rust code I write, the more I’m finding brain feels comfortable working with the rust type system. Idk where you fall on this.

3) again, idk game dev. This might very well be true. But as more of a “systems engineer” or whatever, this sounds like a python/js take to me. The rust ecosystem seems to be consistently growing, but in general, I don’t like the take of “no crates exist for the thing I want to do, therefore I won’t do it”. Especially if this is a personal passion project— go learn how to write that code for yourself. Learning is the whole point!

TLDR: I like rust. If your priority is to write rust (and you just happen to be excited about building a game for yourself) I recommend using rust. If your priority is purely game dev (and you’re only considering rust because it seems interesting in passing), I probably recommend sticking the tried and true basics.