News for hackers. Stuff that matters.
Re:Write plain text files by phreack on Tuesday March 01, 2022 @11:57PM (#30523914)
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.

So, uh, yeah I agree absolutely with you.

Re:Write plain text files by awr on Wednesday March 02, 2022 @07:04PM (#30535294)
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.
Re:Write plain text files by ben174 on Wednesday March 02, 2022 @06:57AM (#30526340)
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:

https://github.com/ben174/bugben

Re:Write plain text files by robin_reala on Wednesday March 02, 2022 @09:05AM (#30527396)
My official CV is a page on my site, that I print to PDF if someone asks for it. The page itself is as source-controlled as the rest of the site.
Re:Write plain text files by thefunnyman on Thursday March 03, 2022 @02:43PM (#30545769)
I do the same by having my resume in latex which I’ve checked in to git. Been meaning to write a GH action to generate the pdf artifact automatically.
Re:Write plain text files by tomrod on Thursday March 03, 2022 @09:24PM (#30549872)
I've decided to migrate my CV to Markdown instead -- pandoc can dump to LaTeX, PDF, you name it.
Re:Write plain text files by chrisfinazzo on Friday March 04, 2022 @10:14AM (#30555933)
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.

[1]: https://github.com/chrisfinazzo/resume

Re:Write plain text files by vertis on Wednesday March 02, 2022 @05:00AM (#30525644)
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.
Re:Write plain text files by Zak on Wednesday March 02, 2022 @10:15AM (#30528251)
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?

Re:Write plain text files by yencabulator on Friday March 04, 2022 @01:18PM (#30558335)
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.
Re:Write plain text files by tracker1 on Wednesday March 02, 2022 @07:24PM (#30535443)
git-lfs with appropriate file types set to use it.
Re:Write plain text files by sslayer on Wednesday March 02, 2022 @11:09AM (#30528876)
LOL,sweet summer child, its all 0's and 1's
Re:Write plain text files by munk-a on Wednesday March 02, 2022 @01:51PM (#30531199)
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).