Inkscape 1.2 released • Hacker News Board

Re: Inkscape 1.2 released

#231

Post by efortis » Fri, May 20, 2022, 10:14 PM UTC

esrauch wrote: post #228

efortis wrote: post #209

Earlier quoted context omitted.

> you'd need to conceptually understand what edits were made Same effort as reviewing the file history > and then make them again manually to the "head" version Copy + Paste

This post is about Inkscape and Inkscape svgs dont have any edit history baked into them. If you had a dozen revisions and one of several collaborators sends you a suggestion version which they edited from some unknown revision what would you do with that? The file itself doesn't imply what deltas they made, and "copy paste" doesn't make sense, since what would you even be copy+pasting?

Do you honestly think there's no way?

Re: Inkscape 1.2 released

#232

Post by esrauch » Sat, May 21, 2022, 10:46 PM UTC

efortis wrote: post #231

esrauch wrote: post #228

Earlier quoted context omitted.

This post is about Inkscape and Inkscape svgs dont have any edit history baked into them. If you had a dozen revisions and one of several collaborators sends you a suggestion version which they edited from some unknown revision what would you do with that? The file itself doesn't imply what deltas they made, and "copy paste" doesn't make sense, since what would you even be copy+pasting?

Do you honestly think there's no way?

Yes, I honestly think that if you have collaborators doing edits forming a DAG of derived artifacts, and you only observe a subset of those artifacts that you can't take some arbitrary artifact and merge that correctly with another arbitrary that opaquely branched some point in the past. And that is what consistently happens with the "just email some zips of the documents" collaboration flows.

Git helps by forcing the deltas to be knowable, but at the expense of a complex management tool and only really working on text based source. All other modern software now solves this problem by being online collaborative which eliminates the problem entirely, and that benefit dwarfs any other feature for most corporate/organizational usecases.

Inkscape is great software, but it's not acceptable software if you're going to collaborate with multiple other people who will all be making edits to the same document.

Re: Inkscape 1.2 released

#233

Post by efortis » Sun, May 22, 2022, 2:23 AM UTC

esrauch wrote: post #232

efortis wrote: post #231

Earlier quoted context omitted.

Do you honestly think there's no way?

Yes, I honestly think that if you have collaborators doing edits forming a DAG of derived artifacts, and you only observe a subset of those artifacts that you can't take some arbitrary artifact and merge that correctly with another arbitrary that opaquely branched some point in the past. And that is what consistently happens with the "just email some zips of the documents" collaboration flows. Git helps by forcing th…

If you wonder how people collaborated (and still collaborate) without this tech let me know.