Yeah, there are LOTS of things I liked about VMS. I was system administrator for our lab system, it was the easiest system to manage.
But when I was using VMS, it was for software development or for editing documents, etc. Versions were quite useful there. These days, I’m not doing any software and not much document editing. And if I am doing serious text construction, I’ll use EMACS (Aquamacs) because of 40 years of muscle memory 
EMACS does its own versioning.
Of course, simple file versioning is no replacement for source code control. If I were doing serious software, I’d want a LOCAL version control system that can manage collections of file versions together. (I don’t trust cloud-anything, including cloud software repositories like GitHub, for critical data.)
(And a true story about VMS: Another guy was the original sysadmin for our R&D lab system. The Vax was brand new, and he was still learning VMS when he queued up a batch job to run overnight. His account had EXQUOTA enabled, and there was an error/loop in his batch job. When we came in the next day, the entire disk was filled up by the logfile from that batch job. Cleaning that up was an experience. And then I told him, “Lesson learned: Always run a job with least privilege.” He was very embarrassed. But fortunately that was just an R&D lab resource so no real time was lost on anything important.)