News for hackers. Stuff that matters.
Re:Inkscape 1.2 released by efortis on Monday May 16, 2022 @08:17PM (#31404583)
Good employees find ways to collaborate no matter what. That’s to say that real-time collaboration is a luxury feature. Also, many projects have only one designer. Not to mention, it’s rare to find designers that work in tandem.

Also, from a dev perspective having designs updates without some process is undesirable.

Re:Inkscape 1.2 released by ageyfman on Monday May 16, 2022 @08:48PM (#31404753)
As a different point of view, I work w/ my designer in Figma, and the collab features are a must-have. Our iterations are much faster in Figma than they would be on static files shipped via PDF, or whatever it would be.
Re:Inkscape 1.2 released by efortis on Monday May 16, 2022 @08:56PM (#31404797)
I've worked with designers in tandem as well, sharing screen, sitting next to each other, and in online real-time. Real-time collaboration is a way to collaborate, not the only way.
Re:Inkscape 1.2 released by ageyfman on Friday May 20, 2022 @11:29AM (#31448801)
these folks are in Western Europe, and I'm on PST. So it's all async.
Re:Inkscape 1.2 released by BeetleB on Monday May 16, 2022 @09:13PM (#31404887)
> Good employees find ways to collaborate no matter what.

The majority are not good employees.

Good employees can collaborate well with LaTeX as well. Yet over 99% of workplaces will not use LaTeX.

Re:Inkscape 1.2 released by efortis on Monday May 16, 2022 @09:23PM (#31404964)
Knowing LaTeX doesn't make you a good employee.
Re:Inkscape 1.2 released by BeetleB on Monday May 16, 2022 @10:24PM (#31405406)
Knowing how to collaborate well with LaTeX makes you about as "good" an employee as knowing how to collaborate well with Inkscape.

The point is that even in places where about half the employees know how to collaborate with these tools, it is not done because you need the other employees to function.

Re:Inkscape 1.2 released by efortis on Monday May 16, 2022 @10:38PM (#31405472)
I meant good as in good faith, but I see your point. I started using Corel Draw ~97, and after trying many design programs of all them seem about the same complexity-wise.

Now, many people tried Gimp (which is far from Photoshop) and they wrongly think that Inkscape is another Gimp.

Re:Inkscape 1.2 released by BeetleB on Monday May 16, 2022 @11:04PM (#31405611)
Amusing you use Gimp as an example, as I've always found its (UI) critiques to be "Not Photoshop" critiques :-)
Re:Inkscape 1.2 released by Gigachad on Monday May 16, 2022 @11:26PM (#31405738)
I have never used photoshop and I still feel unsatisfied with GIMP. I have a long list of thoughts but the simplest one was the fact that moving/rotating/scaling a layer is 3 different tools. I was told a long time ago that there was work to merge them, years later the change comes out and it just groups the tools under one icon so you now have to right click first to select the tool you want. It's pretty much broken on a 4k display as well.

I do like gimp as a bit of a Swiss army knife program, it can do a lot of utility jobs like resizing, outlining, etc which can be hard in some of the more intuitive modern apps, but most of my work now is done on an app like Procreate and then I'll move to gimp for the final edits.

Re:Inkscape 1.2 released by BeetleB on Monday May 16, 2022 @11:49PM (#31405834)
Gimp certainly has its GUI problems - coming back to it after using Darktable has been quite painful. I can accept it has GUI issues. However, for what it does, the only tool that is better is Photoshop. Sure, Lightroom/Darktable has a lot of nifty convenient stuff with a better GUI, but they're simply not a viable replacement for Gimp.

There are other photo editing tools with better UI, but poorer features, sadly. It would take a ton of work to catch up in terms of features.

Re:Inkscape 1.2 released by prokoudine on Tuesday May 17, 2022 @11:20AM (#31412025)
> I have a long list of thoughts but the simplest one was the fact that moving/rotating/scaling a layer is 3 different tools.

You might find that fact to be on the ageing side :) Unified Transform tool has been available for many years now. It's all three (and more) tools in one.

Re:Inkscape 1.2 released by kevin_thibedeau on Monday May 16, 2022 @11:41PM (#31405805)
If anything Gimp is too much like Photoshop. Corel Photo-paint has a much more powerful paradigm of manipulable bitmap objects rather than shoehorning everything into fixed dimension layers. It's unfortunate it never got any respect and withered.
Re:Inkscape 1.2 released by funstuff007 on Monday May 16, 2022 @09:23PM (#31404962)
Of course, if an employee is crummy, you'd want to silo their work product so it did not infect the rest of the org.
Re:Inkscape 1.2 released by BeetleB on Monday May 16, 2022 @10:23PM (#31405401)
The point is that few workplaces have a majority of employees that are "good enough" to find ways to collaborate with Inkscape. If even a third of them cannot find a way to do so, you're stuck, and siloing your/their work is not an option. No decent manager would accept that merely because you insist on using Inkscape.
Re:Inkscape 1.2 released by ClumsyPilot on Monday May 16, 2022 @08:38PM (#31404699)
"That’s to say that real-time collaboration is a luxury feature."

So were toilets once upon a time.

I am not a fan of webapps, but this line of argument doesn't hold water

Re:Inkscape 1.2 released by efortis on Monday May 16, 2022 @08:49PM (#31404760)
I rather have a toilet than saving two clicks.

—-

real-time collab is not exclusive to webapps.

Re:Inkscape 1.2 released by Gigachad on Monday May 16, 2022 @09:00PM (#31404822)
>real-time collab is not exclusive to webapps.

Sure, but once you make the effort required to build a real time app, there are vanishingly few reasons why not to have it as a web app. Some of them provide a desktop app as well but they all provide a web app.

As a designer, you can just send a link to your design to anyone, end users, clients, developers, managers. And they just click it and it shows up and works. No need for installing software, setting up accounts, etc. A lot of these web apps are actually C++ and then compiled to web assembly so they are quite fast.

Re:Inkscape 1.2 released by esrauch on Tuesday May 17, 2022 @07:28AM (#31408875)
Do you use source control or do you email zips with the source files between you and the other developers? The collaboration here is exactly the same as that distinction in workflows.

It's obviously not just "two clicks", it's "Text copy 2 final final alt reviewed.doc" and then you get a new person email their suggested updates to you as "Text copy 2 final 2.doc" and you have to somehow merge those suggestions in with the head version.

With Word at least there's the ability to do suggestions rather than direct edits to let you collaborate against nonsynced docs at all, but with Inkscape when that happens you'll literally just get a different svg and you can't actually merge at all, instead you'd need to conceptually understand what edits were made and then make them again manually to the "head" version, which is completely redundant work.

Re:Inkscape 1.2 released by efortis on Tuesday May 17, 2022 @12:07PM (#31412712)
> 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
Re:Inkscape 1.2 released by esrauch on Wednesday May 18, 2022 @05:42PM (#31428029)
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?
Re:Inkscape 1.2 released by efortis on Friday May 20, 2022 @06:14PM (#31453169)
Do you honestly think there's no way?
Re:Inkscape 1.2 released by esrauch on Saturday May 21, 2022 @06:46PM (#31462815)
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 by efortis on Saturday May 21, 2022 @10:23PM (#31464335)
If you wonder how people collaborated (and still collaborate) without this tech let me know.
Re:Inkscape 1.2 released by ClumsyPilot on Tuesday May 17, 2022 @08:04AM (#31409220)
Actually desktip Word has realtime collaboration these days, although getting it to work can be challenging
Re:Inkscape 1.2 released by fivelessminutes on Tuesday May 17, 2022 @01:05AM (#31406245)
On my deathbed, I doubt I will be regretting not bending my life out of shape more so someone would call me a 'good employee'.