This will also be a bit messy, as I am on my phone and don't have much time to write this down. I have 10 years of writing Java on both small hobby projects an

This will also be a bit messy, as I am on my phone and don't have much time to write this down. I have 10 years of writing Java on both small hobby projects and massive systems on my job. I dipped my toes into C/C++ a few times and I can write hobby project sized code that runs, but I can never really trust that code like I can the Java code that I write. I had this issue especially when writing my first TeamSpeak Plugin: I could never be certain if I had to free the data or if TeamSpeak would do it for me after my function was called. I had to look into the documentation, as TeamSpeak is closed source. About one and a half years ago, I finally sat down and learned Rust. I had tried to learn it several times before and always ran out of motivation. This time, I got to hobby project level proficiency within a month or two. It was really fun and I rewrote several Java Spring projects in Rust's Rocket. As Rocket starts just about instantly, even with the long compile times, the Rust rewrite takes less to compile than the Spring projects took to start up. Coming to the point: I am already more confident about my Rust code than ever was about C and would even go so far as to say that I trust it more than my Java code, despite the big difference in experience. I believe that I am ready to jump into a big Rust codebase and become productive as soon as I have understood the business-logic of the project in question. I doubt I will be able to say the same about C/C++ in the near future.