> You're right that the language itself is pretty stable and doesn't make breaking changes. Regardless, right now, we're clearly talking about the community and

> You're right that the language itself is pretty stable and doesn't make breaking changes. Regardless, right now, we're clearly talking about the community and libraries No, I know. I am talking about community/libraries too. > If a library has been on version 3.x for the past few years, I have some indication that there's some commitment to API stability. As you also do if a library has been on version `0.2` for the past few years. As is the case for `libc`. Or `0.4` for `log`. Notice that you aren't actually using just the version number. You are making an inference about release cadence to draw a conclusion. Contrast that with the essential communicative role of semantic versioning, which is that it communicates something about the content of the change: whether it's breaking or not. That truly can be read straight from the version number exclusively. But "stability" or "maturity" cannot be. Your comment is making my point for me IMO.