this post was submitted on 15 Sep 2023
30 points (75.9% liked)

Rust

5398 readers
49 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

[email protected]

Credits

  • The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
30
Should I Rust or should I Go? (kerkour.com)
submitted 9 months ago by [email protected] to c/[email protected]
21 comments fedilink hide all child comments
 

I think some raised points are relevant...

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 12 points 9 months ago* (last edited 9 months ago)

I'm of course only one single anecdotal sample, but the release cadence has probably been the least of my problems. My experience is that it's fine to not update for quite some time. I have a crate with 1.60 (released about one and a half years ago) as MSRV, which means I run unit tests with that version, as well as stable, beta and nightly. The only pressure to upgrade is that some dependencies are starting to move on. Not that the newer compilers reject my code, not even anything deprecated.

Also, small, frequent releases usually takes away a lot of the drama around upgrading, in my experience. Not the opposite. A handful of changes are easier to deal with than a whole boatload. Both for the one releasing and for the users.