💾 Archived View for soviet.circumlunar.space › wholesomedonut › gemlog › learning-rust.gmi captured on 2023-09-28 at 16:35:04. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-12-03)
-=-=-=-=-=-=-
date: Thu Jan 14 01:38:23 UTC 2021
And I've gotta say I enjoy it.
I got ahold of "The Rust Programming Language", from No Starch Press. On top of
detailing how Rust does things in specific, it serves as a nice crash course
or reminder for basic programming concepts and structures like memory safety
and the logic behind primitives.
Thus far I've been fairly intrigued. I don't know what it is, but I like Rust a
lot more than C++, which seems to write very similar code syntactically.
Considering that I've spent a decent amount of time now having written both
languages' code in a terminal editor like nano, and then debugged and compiled
it from the command line, I'd take Rust and 'rustc' over C++ and 'gcc' any day
of the week! It's so much more helpful. There's a fairly spartan, almost elitist
view that I get from a lot of systems-level programmers familiar with C-based
languages; as if wanting to feel miserable for having to look up yet another
compiler or linker error's cryptic meaning is preferable to having the compiler
spell it out for you clearly so you can fix it.
Not that I've gotten that vibe from YOU, dear reader. But you get the point.
I like the re-hash of tried-and-true concepts that rust is built on, as opposed
to the artificially limited, outdated way of doing things in C/++ natively.
Not to mention ownership is friggin sweet, screw manual memory management. Out
of scope == out of mind!
Now to see what meaningful projects and applications I can develop with it to
sharpen my skills and get some real mileage out of the language.