hmm.. i'm interested.
however, when you say files (with an 's' at the end), do you mean having a different file for each desired version?
because if so, that's definitely not the sweet solution..
(like, with multiple files as the versions, i could just use the doc name as the descriptor.. just like i did for the decade prior to osx versioning

)
or, does this suggestion work in conjunction with Versions?
(but, without the GUI, it's probably a no-go for me.. with versions UI, you can go back in time, copy an object, come back to the present, and paste that object.. all without leaving the current document or going to a file structure or opening another doc.. etc)
No, you don't have one file per version. You can have a project with multiple files in a folder, and check in all the files in that project. If you only have one file per project, then you only check in that one file, and you only have that one file as a working copy. If you want you can revert to an older version of the file.
There are some differences between git and Apples Versions. Apples Versions have a guy that is like TimeMachine backups. You don't get that kind of guy with git. Look at the screenshots on the page I linked to in my previous post. With Versions you can just have a simple timeline. You save a document, and can't add notes. When you save the next time, you have two versions of the file, and can choose go go back or forward in your history. With git you can create branches, which is often used by programmers.
You can see it on the first picture on
https://www.sourcetreeapp.com in the table view under the Graph column. So you start by checking in the first version of your document. Let's call it version 1.0.
Then you make an update and check in that one. Sometimes you might want to split the versions. In the case of programming you make a branch to add a new feature, and another branch can be for bug fixes. I guess you're not a programmer, and I don't know what purpose your documents serve, but let's say they're presentations, and you create your initial presentation and save it. Then you split it so you can have a branch for the presentation for a specific audience, and you can jump back and forth between the branches. Let's say your presentation is for a new medical drug. You enter all the information in the document that are common for all your audiences. Then you make one branch for changes to the presentation intended for medical doctors, and another branch for the presentation of the drug for patients.
Later on you can also merge the two branches, so that all the changes for each branch end up in the same document. I don't know if you understand what I mean. It's hard to explain without doing a demo. You can download SourceTree and try it out yourself. It's free, so you don't lose any money, just some time to evaluate the app.
One drawback with git though is that it creates an "invisible .git folder (which contains the database for all the versions) for the "project", even if the project is just one document, which means you can't have all your documents in the same folder, because git can't create one .git file for each document then. So it's best to put each document in it's own "project" folder.
[doublepost=1495860679][/doublepost]
Also, I long for the days of screen sharing and remote controlling another mac after being given permission in Messages.
You can do screen sharing and remote controlling in Messages. If you have a conversation going, then you can see the name of the one you're communicating with to the left in the window. Right click on the name and either select to share your screen or ask your friend/colleague to share their his/her screen. Then one of you can "see" the other persons screen. In order to control it, there's a button in the toolbar of that window, and when clicked the other part must confirm that he/she accepts to get the screen controlled.