You could be; there’s not much way for anyone here to tell for sure one way or the other. Learning is also a skill which takes time and practice to become good

You could be; there’s not much way for anyone here to tell for sure one way or the other. Learning is also a skill which takes time and practice to become good at. Incidentally, in order to write a good C++ program it is necessary that you follow pretty much the same rules that the borrow checker enforces. The difference is that in Rust the compiler tells you when you fail to do this, while in C++ your program just crashes, or corrupts some data, or has race conditions. You could feel like you’re making a lot of progress in C++, only to end up with a program that is a buggy unstable mess. The alternatives are to either face the pain up–front, or to use a language with garbage collection. For most tasks, garbage–collected languages are actually the superior solution. This is because the time we spend writing a program has a cost, and that cost is frequently greater than the extra cpu cycles spent scanning the heap or waiting for locks.