I once thought git for humans would be a great idea but never got around to speccing it out. Later on, a lawyer friend showed me the software they used 'for backup' (that they paid thousands per month for) and it turned out everything about it was just exactly like SVN. The terminology was different, the UX was laser focused to the intended users, but at the end of the day it was commits, syncs, merging, pretty much everything but branches, just laid out with domain specific language instead, professional office UI and simple UX.
What was the tool called? We're currently looking to solve a problem for a client to better manage contract negotiation between his lawyers and the purchaser's lawyer (apartment units). ATM it's all done via email but I imagine there'd be heaps of tools out there.
I tried to git my resume once upon a time. It's still something I'd love to finish doing, it just makes sense to have a git repository as a timeline of your life:
I eventually settled on LaTeX - although I considered dropping all the way down to groff/troff and having TeX be an intermediate step in the process.
Custom LaTeX classes made this more trouble than I was willing to deal with, so I decided to not pursue it further. I suspect Markdown might have similar challenges dealing with this, although given that the "verbose mode" is just HTML, I might be able to make it work.[1]
The print media type has been around for eons, but the @page rules don't support everything I need and are generally absent in WebKit browsers.
Enterprise Content Management like EMC Documentum has this sort of thing baked in (it's been a long time, but they're definitely on top of it). But that's for big companies.
I had a similar thought some time ago and concluded it's an impossible task. The problem is that it would need to understand every file format its users care about and be able to represent changes in a useful way.
How do you merge destructive edits to image files?
Many version control systems aimed more toward digital assets do some sort of locking, so only one user edits a file at a time. Advisory or mandatory, with support for breaking locks, etc.
Please explain, in 0's and 1's how to combine the change to add a dark splotch over here and a patch of blue over there so that the image you get out of the merge has both the dark splotch and the patch of blue... without teaching git how to comprehend image file formats (and assuming you're not using a bitmap which is sort of a free win).
So, uh, yeah I agree absolutely with you.