Post AwpWI2GQJroeaO3itM by lanodan@queer.hacktivis.me
 (DIR) More posts by lanodan@queer.hacktivis.me
 (DIR) Post #AwpWI14gk0pothYpxg by bugaevc@floss.social
       2025-08-04T13:48:10Z
       
       0 likes, 0 repeats
       
       Do you use Git CLI, despite there being a large variety of UI apps for Git? (So do I!)Why is that? What are they all missing? What would make a Git UI app work for you?Is it "not exposing important Git concepts"? (which ones?) "Dumbing things down"? (how?)
       
 (DIR) Post #AwpWI2GQJroeaO3itM by lanodan@queer.hacktivis.me
       2025-08-04T15:16:34.880285Z
       
       0 likes, 0 repeats
       
       @bugaevc Mostly because so far I haven't needed GUIs.And even though git is decentralised, I still tend to ssh to another machine even for regular dev because I'm not a huge fan of having WIP branches on different machines, makes it hard to know for sure which is truly the most recent sometimes.
       
 (DIR) Post #AwpWKnFGcBUosJpiKW by aurisc4@floss.social
       2025-08-04T15:11:27Z
       
       1 likes, 0 repeats
       
       @bugaevc I use CLI because it talks to me when something goes wrong.And I love to focus on writing code without thinking about committing it and deal with committing when logical conclusion point is reached. So far all GUIs feel like it's too easy to make a mistake in such work style.Oh, and I do use git on 3 different OSes, so CLI is the same in all of them.
       
 (DIR) Post #AwpZblWkYUfoKenMg4 by bugaevc@floss.social
       2025-08-04T15:50:44Z
       
       0 likes, 0 repeats
       
       @lanodan okay yeah, remote dev is a good point. So potentially this would be better if more UIs for Git supported remote repos over SSH or something?
       
 (DIR) Post #AwpZbmTb1hkFHAKMOu by lanodan@queer.hacktivis.me
       2025-08-04T15:53:46.983830Z
       
       0 likes, 0 repeats
       
       @bugaevc Well there is sshfs, so they don't need to.Although usually if you're going to work on remote files you also want the remote context (like having the right toolchain).
       
 (DIR) Post #AwpaKPNZkQ22fln7fk by bugaevc@floss.social
       2025-08-04T16:01:16Z
       
       1 likes, 0 repeats
       
       @lanodan yes, but actually no. Git does a lot of file access (naturally), both in the working tree and inside .git, and doing it sequentially is going to be dog slow over sshfs. You either need to run a backend (e.g. git CLI) on the remote, so it can run its logic there and only send the useful output (e.g. the list of modified files) over the network, or have some latency-aware Git implementation that would access all the files concurrently.And yeah good point about the toolchain too.
       
 (DIR) Post #AwpaXjj5PS27XgCxsW by lanodan@queer.hacktivis.me
       2025-08-04T16:04:16.752783Z
       
       0 likes, 0 repeats
       
       @bugaevc Ah yeah I can see that problem with sshfs, reminds me that I often use find(1) on the machine the files are on and then copy-paste the result, rather than do the find(1) on the machine my hands are on.