Ask HN: Going All-In on Rust
I am a full-time engineer working for an MNC where the tech stack is Java / Python. Outside of work, I spend most of my time in competitive coding and teaching programming to friends/family.
I am looking to transition to Rust for all my side projects (and possibly everywhere in the near future). I don't have any specific reason for this transition other than to move away from Java / Python.
I want to continue my competitive coding practice and my side projects that are mostly low-level systems. I am looking to build a niche for myself and see Rust as an escape (something I can explore and grow with). I might be overplaying my hand here, any suggestions would be helpful.
Is there anything to keep in mind before I take this plunge?
18 comments
[ 2.9 ms ] story [ 51.5 ms ] threadFor that type of problem: ie. it's more finding the algorithm than the code itself that matters, the solution will probably be less than 1000 lines of code and there's only one person working on it, I think it's hard to beat Python. Worrying about static typing let alone memory management will probably only slow you down and maybe even interfere with the thought processes needed to find the right algorithm.
I say that despite actually not liking Python very much and this advice is the exact opposite of what I would give someone looking for a language to use on a large code base that needs to be maintained over time by multiple developers.
https://www.amazon.com/Programming-Algorithms-Lisp-Efficient...
Perhaps there is a different language that can fit the bill.
I adopted rust a while back and have since ported basically everything to it, even at work. It’s my new best friend, for sure.
The best advice is just to keep going.