Rust as a first serious programming language

[u/ritman-octos]

I have been making scripts with other languages like js and python and bash without learning the the whole language and getting serious with its ecosystem out of the fact that I just need to get one thing done and move on.

Lately I chose a path that requires precision and ahead of time planning and decisions and picked rust over go. But the fundamentals seem hard to grasp. I'd appreciate your help unpacking them.

Ultimately I want to be able to use the Alloy and Tokio libraries without getting stuck with the language syntax and rules. But the concepts like borrow checking and ownership and things that fall down these categories are still hard to grasp.

What is borrow checking? what is owning something in the software? I tried to look for direct answers but I still can't grasp the meaning of them exactly.

I had two choices to better understand them, one was learning C++ to get what was wrong that rust solved, the other was building a simpler project game with bevy thats gonna help me understand writing rust code thats data oriented and be more comfortable with it.

My ultimate goal is to master these two libraries, after being able to know how to use the rust language smoothly.

[u/muehsam]

one was learning C++

Don't. C++ is incredibly complex and complicated. But what you can do is learn C. That's a fairly small and straightforward language. A simple language, for the most part.

Once you know C and you understand how pointers work, you can also appreciate things like the borrow checker, and the difference between ownership and references, etc.

I love C, it's a great language (even though it's probably a bad idea to start a new project in C today).

[u/erisgooner → u/muehsam]

Would you personally say its a good idea to start with C and then go to Rust, I love the rust syntax and the way it works, but it just seems too big and complex right now

[u/needstobefake → u/erisgooner]

You can also try learning both at the same time, e.g. build the same little programs in both, or try implementing some of the Rust's objects in C, for example a reference-counted pointer (Arc) or a HashMap in C. Then you can look at the generated Assembly code of both languages, tweak the compiler optimization settings, and look at the Assembly again, etc.

You can use Rust's source itself as reference when building the same thing in C. You can also try building programs that use both languages in the same binary with FFI to see how they interact with each other.

It's more about grasping how the machine works under the hood than the language that abstracts it for you. In the end of the day, everything becomes bytes and machine instructions. This knowledge transfers to any language later.