Rust

Ignore the reasonable comments that say you are more than ready.

The next step is obviously learning Haskell, specifically sum types (like rusts enums), lists (lazy, like rusts iterators) and classes (like rusts traits).
Then you will think, "if only there was a language that was a mix of C and Haskell" and that's rust.

I see that other comments reflect what I would say, so I would like to just congratulate you on your perseverance to spend 6 months on preparatory learning. The way I learn I just parachute straight into the deep sea, and then go into rabbit holes when I don't understand how something works. Spending some time beforehand to learn background is probably a wiser idea, giving you a more rounded understanding. But I just can't do it

So salutes to you and godspeed!
Now go and get yourself that cargo ;)

Just start using Rust. You can read for years and years about stuff, but it’s much more useful to just start USING and DOING.

Just read The Rust Book. It's free, and you're more than well-prepared.

Then when you finish that, get Rust for Rustaceans.

Or if books aren't your thing, there are some alternative learning methods on the Rust site.

These are all very useful things to know about, but besides maybe the difference between stack and heap, they are not things you need to learn about before getting starting with Rust.

So if you actually do want to learn Rust, then that's your next rabbit hole

The next rabbit hole is to start learning rust.

As long you understand the stack you’re good to go. It will help you understand why the borrow checker is like the way it is.

I would, first and foremost, try to understand the science behind oxidation. /s

I don't see anything as having to come before learning Rust.

If something about Rust requires more technical knowledge, then that learning is part of learning Rust, even if you could have learned it separately beforehand.

Better start learning Rust to get in there instead of delaying, which adds risk to never arriving, loss of interest, or lack of progress on the goal of learning Rust, with a lack of satisfaction.

Once you learned Rust, you can look around to gain broader knowledge and expertise, if you want, but that's not necessary to learn and make use of Rust.

I agree with the many others who say you're more than ready to start learning rust. I would add that if you've brushed up against manual memory management in C, then you might find the following a great introduction to rust and the borrow-checker: https://rust-unofficial.github.io/too-many-lists/

As usual for discussions about starting to learn rust, I would also recommend the "special"/experimental version of The Book maintained by Brown University: https://rust-book.cs.brown.edu/title-page.html . It has little interactive quizzes that help check your understanding, and some fancy diagrams in the sections on pointers and the borrow-checker.

Sounds like you know plenty to learn Rust.

I've been a developer for over 20 years now and I've never done anything meaningful in c or c++. My c was mostly working through an old book as a kid and later 1 uni course and my c++ mostly some limited game modding. I had no particular issues learning rust and writing stable production code in it. I don't think there's a wrong time to start

You can learn Rust whenever you want. There's no rule that you must learn anything (including C) before learning Rust. Of course, knowing C will make the basic concepts, especially around memory management, a lot simpler.

If your goal is to eventually learn Rust, your next rabbit hole should be the book ideally. If you prefer a video format, I don't have any specific suggestions since I don't learn through videos usually, but I know there's some good video resources on YouTube.

Learning C first is great, just because C is a great language. But learning to avoid shooting yourself in the foot is not a good reason. You could do that with rust, where you can also shoot yourself in the foot, or assembly where it’s even easier.

The list you put together is great and Core Dumped is an awesome resource.

Number one suggestion from me as always and as many others… write something. If there is anything about which you have domain specific knowledge, write something related to that, so you can focus on growing your expertise in programming, not in another primary field at the same time.

I would also definitely recommend to get started with learning Rust. You will need to learn more concepts along the way, but you can still learn about them while you're coding Rust.

Or rather: I always found it most productive to learn about concepts, while I'm actively using them in a project. So, I would even recommend to jump into Rust now, try to tackle a few smaller projects, and then continue learning general concepts later.

The bible /s