3 ms·
Thanks for writing this Paul; Rust is not going to be for everyone, and it's always nice to see reasoning laid out. For whatever it's worth, I wish I had more
by steveklabnik 6y ago
Thanks for writing this Paul; Rust is not going to be for everyone, and it's always nice to see reasoning laid out.
For whatever it's worth, I wish I had more time to contribute some code back when you were asking for examples. It kinda felt to me like a lot of your code was trying to write OCaml in Rust, which causes a lot of this friction. But it was only a feeling; I didn't have the capacity to really dig in. It is also very true that taking time to get up to "what is the Rust-y way to do this" is a challenge for folks learning Rust, and a valid reason to use a language that works closer to how your brain works.
I'm excited to see how F# works out for you; it's something I've always wanted to spend some time with, but never found the chance to actually do so.
- FullyFunctional 6y agoFWIW, I had the exact same experience as the OP; I was slowly getting comfortable with Rust until I wanted (high performance) cooperative multitasking, which in Rust meant getting into Async and all the complexities of Rust multiplied to a point where I'm reconsidering some life choices. And I have yet to match the performance of the C++ equivalent solution :( I suspect I would have liked the original green threads more, despite the drawbacks.