Learning Rust
published:
I've been noodling around with the Rust programming language. Mainly just writing a glorified CS 101 console app, some console I/O, some file I/O, a little SQLite database. I'm not the kind of coder that likes doing this for fun in their spare time, but I wanted a little doohickey to make something easier for me, and so I thought hey why not try out this whole Rust thing.
Not super in love with it, so far.
There's a lot of hand-wringing articles about going to Rust from
The big selling feature is of course the memory safety guarantees, which come as a result of the
ownership model and the move-by-default nature of things, as far as I can tell. I'm not sure it
moves the needle for me, as I think you get more or less the same out of "properly"3 written C++
(embrace value-semantics and RAII4,
aggressively pursuing const correctness, avoid
raw pointers, do not be afraid of templates). Either way, the objective is to turn bugs into
compile errors, and Rust is stricter in enforcement of things, where
But the whole exercise has me reflecting on just how poorly
I still think it's ugly though.
-
Yes I can appreciate the irony of being a C++ guy complaining about ugly syntax. Whisper but actually it's the children who are wrong. ↩
-
But I'm not above cherry picking a random blog post that agrees with me. ↩
-
According to me. ↩
-
The absolute dumbest of acronyms. ↩