Part of my point is, if the software doesn't have a concept of "breaking change" semantic versioning makes no sense, so you might as well just use numbers that change with every release so you can easily refer to when bugs got fixed or, maybe, features got added.
Applications do have the equivalent of breaking change, though. Sometimes literally in the sense that file formats change, but more usually in the sense of having to relearn how to do things, or the removal of features.
