It seems that saving lots of versions to avoid data loss can actually lead to annoyance (if not data loss).
As far as I can tell, the versions appear to be getting pushed into cloud storage and the timeline in chronological order. When the snapshots are large (and presumably on slow or unreliable networks or in the presence of other issues are present) those uploads can be extremely slow (order of minutes per version).
If some user has had a long and frustrating several days fighting with a crashy app then they might become very distressed and frustrated by seeing a long list of outdated versions of their work after the app crashes and is restarted and crashes on load and restarts and crashes one more time for good measure and restarts again (purely hypothetically speaking, of course).
Such a user might begin to wonder if they can really trust the app and cloud storage's data integrity and they might begin conducting experimental tests of the aerodynamicity of MacBook Airs.
One possible way to mitigate such a situation would be to preferentially upload the most recent version and then upload previous versions in reverse chronological order (ideally just uploading smaller compressed deltas from the last successful upload to ensure that file size is more reasonable)