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.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !technology@beehaw.org
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
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.