[EspressoGPT]

Yes, it's worth looking into the language and its concepts. But I think many people feel bad for not knowing or not having tried Rust because the Rust community tends to be very vocal and not quite reserved, and I believe that's a mistake. Not knowing Rust doesn't make you a bad software engineer, as opposed to what some Rustaceans want to make you believe.

[MSFT_Edging]

Not knowing it doesn't make you a bad software engineer, but knowing it certainly will make you better(unless you've been writing CPP for 30 years).

[ykonstant]

>(unless you've been writing CPP for 30 years).

Yup; in that case, I am sorry, there is nothing science can do for you (｡•́︿•̀｡)

[MSFT_Edging]

They're too busy redefining c++ primitives then trying to debug their code to see this. I think we're safe.

[kibwen]

> Not knowing Rust doesn't make you a bad software engineer, as opposed to what some Rustaceans want to make you believe.

Nobody is saying this, despite what some people with overactive persecution complexes want to make you believe. As for prescribing what people should do, I will say that curiosity is an essential part of improving in any field, including software development. Learning anything at all broadens your horizons and threatens to make you better. If you don't know Rust, go ahead and learn it (or anything else that interests you); if you already know Rust, go learn something new. It would be quite silly for someone to assume that no advances to the state-of-the-art have happened since they first learned to program.