Git GUI client. Is there anything to choose from?

Question

git

Good day to all!
A couple of days ago I asked myself the question of finding a gui client to work with git. I'm fine with the console, but sometimes it's easier to use the GUI to make commands run faster and better visualize the state of the repository.
I have been using GitKraken for the last couple of years. It was not very stable, but it performed the main part of the functions, which means that there were no complaints about it. However, with the latest update, it gave a new focus: "private repositories are not supported by the free version". I understand that the developer also wants to eat, but making a paid feature that has been free for several years, as for me, is just dirty. Okay, this is a lyric.
I tried to study the issue, I found several alternatives: source three, smart git, gitahed, github gui.
For the most part - either does not work or is inconvenient (only my opinion, I do not impose).
This raises the question: are there any other options on the market, perhaps even paid ones (I don’t intend to pay the gitcraken in principle), not from the announced list? Can anyone share their experience on this?
Well, question number two, which follows from the first: for example, there are no alternatives at the moment.
I suspect that this may be due to the lack of demand for them. All the same, the git is actively used for the most part by seasoned developers and the console is enough for them.
But, does it make sense to start your own development in this direction? I already wrote my git gui client for work needs. In order not to teach our managers how to use git at work, I wrote a simple utility that only knew how to track the state of a remote repository, make a pool as needed and checkout to earlier commits. Perhaps it makes sense to modify this tool to something more serious? Maybe it even makes sense to make it open source, so that other interested people can join?
I would be grateful for any opinion!

Answer 1

I tried almost all free clients from their site, plus the built-in storm.
I tried to use each honestly for several days.
SourceTree did not find anything more convenient.
But it also has disadvantages:
etc.
But these shortcomings can be tolerated. In other clients, it happens that there are no functionalities, and this is already an ass. For example, line-by-line indexing of changes.

Answer 2

The one that is built into the IDE.
Simple operations are much more productive to do in the GUI than in the console.
But for something complicated, it's better to go down to the standard console client.
Graphic individual clients could not evaluate - I do not see the point in them, the two top options together significantly overlap them in terms of convenience.