I agree with you in general but no in the specific case of C and C++.
It has been proven time and time again that writing secure programs in C and C++ is a task that is too hard for humans so those languages should be retired as soon as humanly possible.
Whether that's with Rust or with go or Java I don't care.
And while doing that you did a little a straw man fallacy
I know like everyone else that neither Java nor anything else is always secure.
I didn't even promote Java, I think each team should decide what makes sense for them.
That could be Rust, Go, Java, Kotlin, I don't have a clue because I don't know that team's context.
My point was that C and C++ are especially unsafe languages and that it's a real issue.
I agree with you in general but no in the specific case of C and C++.
It has been proven time and time again that writing secure programs in C and C++ is a task that is too hard for humans so those languages should be retired as soon as humanly possible.
Whether that's with Rust or with go or Java I don't care.
Java secure? Really?
Before I answer can you describe me what kind of experience you have building large scale and secure C/C++ applications?
I never said I did. I never said C/C++ was secure. I only said Java isn’t secure.
And while doing that you did a little a straw man fallacy
I know like everyone else that neither Java nor anything else is always secure.
I didn't even promote Java, I think each team should decide what makes sense for them.
That could be Rust, Go, Java, Kotlin, I don't have a clue because I don't know that team's context.
My point was that C and C++ are especially unsafe languages and that it's a real issue.
But you offered Java as an alternative presumably because you’re alleging it’s a secure language. My link disproves that. That’s my only point.