Creatives of all kinds: check out this delightful list with dozens of FOSS creative tools for artists, photographers, film makers, game devs, musicians, and more!

ADHDefy@kbin.social to Opensource@kbin.social – 156 points – delightful-creative-tools
codeberg.org

A curated list of delightful tools for digital creatives in a variety of mediums.

23

You are viewing a single comment
View all commentsShow the parent comment

Actually not trying to be a dick or a pedant, but is there a problem with just the git command? I've been using it since git existed so I don't really have anything to compare it to. The idea of finding another client seems a bit strange to me.

While the CLI provides the same functionality, it can be a lot easier to visually parse information or provide direct interactivity with a GUI instead. If you're working on a large project or just want a different way to display the information git provides, it makes things a bit smoother.

Generally I just use VSCode's source control UI when I want a GUI for git. I can't imagine using a standalone GUI for git when all the big editors have their own interfaces.

One thing I've found invaluable about a visual interface is the ability to quickly browse the commit tree. Having a big list of commits that you can sort and click to see the diff of each file has saved me on multiple occasions. I'm sure it's all info you can get from the CLI as well, but I can't imagine it being even half as fast.

I guess I can see that. It's not common I need to do so, but a few times I've went spelunking with git log [file] and git diff sha..sha [file] and I could see that being useful presented graphically.