• 6nk06@sh.itjust.works
    link
    fedilink
    arrow-up
    4
    arrow-down
    1
    ·
    2 days ago

    The command line of jj makes sense and is easy to understand. I have to use graphical git clients because I want to cry every time I have to use its CLI.

    • Dark Arc@social.packetloss.gg
      link
      fedilink
      English
      arrow-up
      3
      ·
      2 days ago

      That’s interesting; I find the git CLI pretty intuitive especially for basic use cases most people would need, but I’ve also used git for 15 years now.

      • FizzyOrange@programming.dev
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        1 day ago

        I find the git CLI pretty intuitive

        You might be the first person to ever say that! How do I delete a remote branch?

      • ulterno@programming.dev
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 day ago

        I have only been using it for ~ 4 years and the UX seems pretty logical even for not-basic cases.

        Maybe because it was only my second VCS[1], it didn’t seem at all problematic to me. On the contrary, every time, I just found myself going “nice”, whenever I found a new feature.

        When it comes to git restore ., well, you won’t use rm -rf * in your working directory, right?

        I haven’t used git based GUIs much. Some of the functions that my IDE provides, I use now and then. Being able to see the git blame for a file, right in place, scrolled to the same line as I was looking at the code, helps quite a bit (and so does the git based annotations).
        But for things like commit, restore, pull, push, rebase and things that will write something, I just use the CLI, because I feel like I know what is going to happen ad that gives me confidence.


        1. the first one being folders with timestamps ↩︎