4 ms·

I have little experience in Golang apart from reading the Tour of Go and writing toy programs, but I have more experience in Rust. In my opinion, Rust is defini

I have little experience in Golang apart from reading the Tour of Go and writing toy programs, but I have more experience in Rust. In my opinion, Rust is definitely worth it, even if at the end of the day I work with other languages professionaly, its principles (ownership, borrowing, safe concurrency) really helped me to improve myself. I started to be productive with it by actually writing code, I have read the book during 3 weeks but I learned much more quickly by confronting myself directly to the compiler after. I also became productive with the right tools (vscode + rust analyzer, rust cookbook, rust by examples), the right crates (regex, lazy_static, anyhow, actix, reqwest ...) and pragmatic principles (sometimes boxing, cloning or using refcell when necessary, in non critical code). As always, use the right tool for the right job, there is a learning curve and more cognitive overhead but I really appreciate working in Rust.

poletopole 6y ago
Thanks for your answer! I'll definitely check out Rust's cookbook. I know many hate PHP and that sentiment is slowly changing, but it's my native tongue (that I learned back in 2008 before Rust and Golang), and the cookbook I bought on it introduced me to many new concepts not exclusive to just PHP. I would say the one aspect about Rust I have reservations about is its reference counting aspects. I feel that subject should have been baked into the language like it is for Swift with syntax but still remain as an optional or advanced feature set. But then again Rust's macro system is more than capable of smoothing out its blemishes. I just wish there was a curated list of Rust macros I could find. Would you by chance know of say a Github repo with a curated list of macros?