Fabio Valentini

https://mastodon.social/@decathorpe

Blue Hat Rustacean 🦀 with a Computer Science degree 🎓

I write Rust and Python, and maintain lots of RPM packages for Fedora Linux. Fedora Packaging Committee (FPC) member. Previously also Engineering Steering Committee (FESCo) member.

Fluent in English and German. He/Him. 🏳️‍🌈🇦🇹🇪🇺

Website: https://decathorpe.com
GitHub: https://github.com/decathorpe
Twitter: https://twitter.com/decathorpe
Instagram: https://instagram.com/decathorpe

Public Key

npub154ch8wd5pln4drhvxjgjht4mjjnjcrg8ejgz7dsl36r8656mg6jstj494f

NIP-05 Address

decathorpe_at_mastodon.social@momostr.pink

Profile Code

nprofile1qqs22utnhx6qle6k3mkrfyft46aeffevp5rueyp0xc0capna2dd5dfg4kylvg

Author Public Key

npub154ch8wd5pln4drhvxjgjht4mjjnjcrg8ejgz7dsl36r8656mg6jstj494f

Show more details

Last Notes

2024-06-13 22:15:26

- reply

It usually doesn't (the "major" version getting big, that is).
The thing that *does* matter is the frequency of breaking changes - and if a project releases breaking changes every 2 months (be it pre-1.0 or post-1.0), that's not a good sign in my experience ...
So when I see a library that's only 2 years old and already at version 12.0.0, I'm just a little suspicious.

2024-06-13 15:14:29

- reply

I'm starting to think were talking about different things here.
Or maybe I just don't understand the "sentimentality" associated with pre-1.0 vs. post-1.0 releases.

2024-06-13 14:36:51

- reply

Do you know that the guarantees provided by semver as implemented in cargo are stronger than those by "plain" semver?
For example, 0.2.x and 0.2.y (where y > x) are supposed to be API compatible, even though they're pre-1.0. This guarantee is not present in plain semver.
The only "burden" usually associated with 1.0 is that projects want to settle on a stable API *before* tagging 1.0 to avoid s ballooning number of post-1.0 major releases.

2024-06-13 08:10:15

- reply

I hope so ...
at least for some of the projects on the 0ver list, they are relatively new and stay on 0.x intentionally to mark that their API or CLI is not stable yet (like ruff)
releasing a 1.0.0 has a pretty high bar attached to it, especially in the Rust ecosystem. it might be *too* high, but I don't think it's a negative per se that some projects want to hone in on a stable API *before* they release 1.0 ...

2024-04-26 13:39:34

- reply

oh no 🤭

2024-04-26 13:15:21

- reply

is there the opposite thing? i.e. what if I want to get *out* of the business of running my own servers (for my own sanity)?