this post was submitted on 30 Sep 2023
109 points (91.0% liked)
Programming
17354 readers
311 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.