Google made it so you would never lose a document and you would have access to any previous version of that document at a whims notice.įrom that moment on, Microsoft was playing catch up in regards to the future of word processing. This method was clunky, caused a massive build-up of unneeded duplicate files and gave rise to versioning issues (already handled by Microsoft Word).Ĭoupled with the original autosave feature, version history now provided a solution to users who were tired of backing up and copying files before making changes. With autosave and without version history, the changes made were permanent.Īt first, the way around this was to always make a copy of the document before making edits so you had an old version in case the changes needed to be reverted. What happens if you work on a document for a of couple hours and then decide that you no longer want to keep those changes? With autosave, however, a new problem arose. This wasn’t an issue with Google Docs because in 2013, with it’s very first release, Docs came with an autosave feature that essentially made losing documents by forgetting to save, a thing of the past. One of the main purposes of Microsoft’s version was to keep documents saved in case there was a power outage. Microsoft had already been using a “revision history” feature in the local version of Microsoft Word. When Google first released version history for docs, it was quite a big deal. There are, however, a couple of workarounds that can help hide it or even get rid of it completely. There isn’t a built-in method to just erase or turn off version history.
Learning how to get rid of version history in Google Docs can help save you from being micromanaged and keep the details of your work more private.
Learn how to get rid of version history in Google Docs and discover methods to hide it from collaborators.
0 kommentar(er)
