The one thing that takes a bit to get used to is the borrow checker. Advice there is don’t fight it. Trust the compiler to tell you your code is wrong. Once you understand the ownership/borrowing rules, it’s honestly just a joy to code in. Static typing protects you from the inevitable mess that every large python project becomes, and the borrow checker gives you the comfort and safety you’ve come to expect from memory safe languages without the overhead of a garbage collector.
Still working on this, help is welcome :)
Unfortunately I don’t know shit about Rust. I use Python/PowerShell/Bash/some C#/etc daily for my job, but I haven’t touched Rust at all.
What would you say the learning curve would be based on the languages I’ve worked in?
The one thing that takes a bit to get used to is the borrow checker. Advice there is don’t fight it. Trust the compiler to tell you your code is wrong. Once you understand the ownership/borrowing rules, it’s honestly just a joy to code in. Static typing protects you from the inevitable mess that every large python project becomes, and the borrow checker gives you the comfort and safety you’ve come to expect from memory safe languages without the overhead of a garbage collector.
Ok. I’ll give it a try some time this weekend, thanks for the tip. Hopefully I can contribute in the future.