Opensource

10 readers

1 users here now

This magazine is dedicated to discussions on open source software, hardware, and technology. Whether you are a developer, a tech enthusiast, or simply interested in the philosophy of open source, this is the place for you. Here you can share your knowledge, ask questions, and engage in discussions on topics such as open source programming languages, operating systems, hardware, and more. From the benefits and challenges of open source to the latest developments and trends, this category covers a wide range of topics related to open source.

founded 2 years ago

188

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! (codeberg.org)

submitted 1 year ago by ADHDefy@kbin.social to c/opensource@kbin.social

27 comments fedilink hide all child comments

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

you are viewing a single comment's thread
view the rest of the comments

[–] elscallr@kbin.social 6 points 1 year ago (2 children)

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.

[–] rehendix@kbin.social 5 points 1 year ago (1 children)

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.

[–] HeinousTugboat@kbin.social 1 points 1 year ago (1 children)

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.

[–] rehendix@kbin.social 1 points 1 year ago

Oh same here, I'm not sure what the use-case for a standalone one would be but I definitely do prefer some visual over the command-line trees.

[–] tonamel@kbin.social 2 points 1 year ago (1 children)

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.

[–] elscallr@kbin.social 2 points 1 year ago* (last edited 1 year ago)

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.