I agree that version "naming" is the worst possible option for identifying versions. If you're tempted to go that route, just use the release date as the version number. At least that gives some useful information.
But as a user, I really prefer semantic versioning. Knowing the general scope of the change is very useful to me. If the new version introduces major changes, then I want to be able to schedule the update for a time when those changes won't disrupt me too much. My desire to avoid disruption is exactly why I have grown to hate automatic updates.
But as a user, I really prefer semantic versioning. Knowing the general scope of the change is very useful to me. If the new version introduces major changes, then I want to be able to schedule the update for a time when those changes won't disrupt me too much. My desire to avoid disruption is exactly why I have grown to hate automatic updates.