4 ms·
Just a recommendation, but learn Rust first. Once you have a good intuition about mutability xor aliasing (which is what the borrow checker enforces), you'll ac
by habitue 3y ago
Just a recommendation, but learn Rust first. Once you have a good intuition about mutability xor aliasing (which is what the borrow checker enforces), you'll actually write better C and C++ code should you need to.
Personally, I think Rust is the future of systems programming and there's no more reason to learn C / C++ than there is a reason to learn FORTRAN or COBOL (specifically, the reason is only ever "I need to get a job using those languages"). But, you know, feel free to take that with a grain of salt and see for yourself.
Rust isn't going anywhere any time soon given how many big companies use it, so even if you learn C/C++ first, you'll likely need to learn rust as well eventually if you want to do systems stuff.
- shenman 3y agoIn my opinion, it's better to learn C first because it forces you to do a lot of painful memory management manually. You tend to really appreciates Rust's features when you understand how things can go wrong. Need absence to value presence.
- habitue 3y agoI kinda disagree, I learned assembly after I learned C and I felt like I still appreciated it
- Scarlxd 3y agocan you please share how you actually learned assembly and the resources you've used for it?
- habitue 3y agoIt was in college, had a couple of courses that involves writing some things in assembly. There's not a lot to assembly, but when you write it you realize how function calls involve a bunch of arbitrary choices, and the stack is part of the c runtime, etc. I definitely wouldn't call myself an expert, but the experience was illuminating coming from the world of higher level languages.