That’s interesting. Usually when I see people talking about Rust, they really like it. Are there specific parts that make it less enjoyable than go for you?
For me, it’s the instability in Rust that makes it less attractive than go. By instability I mean that the language itself and the whole ecosystem around it seems to be in a constant flux. If you contribute a PR today you’ll get a review tomorrow saying that “you can now use this and that feature from the latest nightly to save 3 lines of code”, continuing like that for another two weeks before you finally give up.
Go has been the paragon of stability and professionalism since its first release, also due to the fact that it was a specific goal for the language. Additions are slow and few, often thought over and debated for months (or years) to find the simplest, most optimal solution. What’s even more remarkable, they have managed to transport this mindset into the larger ecosystem, which now practices the same values of consistently and quality.
So for me, it feels like the Rust community spends a lot of effort on keeping up with the language, the Go community spends that time getting things done, which is what I mostly go for these days.
I was unclear for the sake of brevity. I LOVE Rust, but I regularly get knocked out of the zone by it, which reminds me I’m programming. That is purely due to my lack of experience with it. I suspect if my chops were as good as with some other languages I’d be having more fun but I’m still wrestling with the compiler quite a bit.
Also, my Go environment and editor config are just better, so I need to get my nvim config up to ship shape for Rust.
I have really enjoyed the small projects I have written in rust but, being in the SRE space, it would be irresponsible and selfish to use anything other than bash, python, or go. It feels like the overwhelming majority of tools I use these days have been written in go.
That’s interesting. Usually when I see people talking about Rust, they really like it. Are there specific parts that make it less enjoyable than go for you?
For me, it’s the instability in Rust that makes it less attractive than go. By instability I mean that the language itself and the whole ecosystem around it seems to be in a constant flux. If you contribute a PR today you’ll get a review tomorrow saying that “you can now use this and that feature from the latest nightly to save 3 lines of code”, continuing like that for another two weeks before you finally give up.
Go has been the paragon of stability and professionalism since its first release, also due to the fact that it was a specific goal for the language. Additions are slow and few, often thought over and debated for months (or years) to find the simplest, most optimal solution. What’s even more remarkable, they have managed to transport this mindset into the larger ecosystem, which now practices the same values of consistently and quality.
So for me, it feels like the Rust community spends a lot of effort on keeping up with the language, the Go community spends that time getting things done, which is what I mostly go for these days.
I was unclear for the sake of brevity. I LOVE Rust, but I regularly get knocked out of the zone by it, which reminds me I’m programming. That is purely due to my lack of experience with it. I suspect if my chops were as good as with some other languages I’d be having more fun but I’m still wrestling with the compiler quite a bit.
Also, my Go environment and editor config are just better, so I need to get my nvim config up to ship shape for Rust.
In summary, skill issue.
I have really enjoyed the small projects I have written in rust but, being in the SRE space, it would be irresponsible and selfish to use anything other than bash, python, or go. It feels like the overwhelming majority of tools I use these days have been written in go.