That sinking feeling that it's gonna be real hard going back to #Python, or even other compiled languages like #Golang, after having already gotten so used to the comforting embrace of the #Rust compiler.
@bitprophet I've found I bounce between rust and python a bunch. Rust is influencing my python a lot, generally in positive ways. I feel like I bias to the right tool for the particular job at hand.
@Twirrim yea I'm expecting it to influence my Python a lot. I had already gotten some slight exposure to mypy etc but I bet I'll get more into them soon.
@bitprophet I’ve embraced the contrast. Rust for the serious “I need to KNOW” stuff. Then coming back to Python for the ease and flow. I’m having fun leaning back into Python’s more dynamic bits, which I’d dutifully held at a distance for too long. It’s a happy mix. YMMV.
@bitprophet I kinda bounced off of Rust when I got 500 lines into my program and realized that to add a feature I was going to have rebuild the entire memory model from scratch again.
@EMR it may, or may not, be a testament to the flexibility of the language that I'm sitting here going "memory model?” - I haven't had to think about anything memory related besides satisfying the borrow checker in a few pretty mild ways, so far. (~660 SLOC right now, apparently.)
What is your “native" runtime? I'm coming from high level interpreted languages primarily, and I have this nagging sense that Rust looks very different to C/C++ people (for example).
@bitprophet I daily Python but I learned C and C++ before Rust so I definitely had that set ot expectations rattling around.
But yeah, satisfying the borrow checker, then lifetime annotating the whole thing, then realizing to add more mutability I should just be storing everything in a hashmap and decided I didn't need that program so badly after all.
Granted, it was sort of a worst-case problem domain for Rust.
@bitprophet and to Rust's credit, I am tempted to go back to that program every once in a while. I think about how good the ergonomics are... Then I run the compiler, see the number of errors, and end up doing something else.
I've been treating this specifically as a learning experience / departure from my typical Python "you can do anything you want" mindset, which is probably why it has been more illuminating than irritating so far.
That plus having internalized the "this is the tradeoff for all the extra safety" angle.
@codemonkeymike s/rough/tough/ 😂 literal tough love! the whole “once it compiles cleanly and your tests pass, you know there's really not much to worry about" thing is real.
Add comment