• oce 🐆
    link
    fedilink
    arrow-up
    17
    ·
    1 year ago

    It was conceived for experts so the new user experience is shit and the UI is not intuitive. But it has become such a widespread standard that it is very hard to completely overhaul the UI.

    • sheogorath@lemmy.world
      link
      fedilink
      arrow-up
      9
      ·
      1 year ago

      TBH compared to the old versioning system people used to use like SVN and Mercurial. Git is a godsend. Just taking your time in learning and not using a GUI client works wonders in learning how it works. Especially when all the GUI clients are basically a collection of commands being executed so if you fuck things up on CLI you know what happened vs using GUI.

    • Pxtl@lemmy.ca
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      Even for experts the user experience is shit. Too much has to be done manually when the default should be automatic, like fetching before pull, recursing when working with repos that use submodules, allowing mismatched casing on case insensitive filesystems, etc.

      • oce 🐆
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        Submodule commands are such mess, which is sad because it is a great feature.

    • roastpotatothief@lemmy.ml
      link
      fedilink
      arrow-up
      3
      arrow-down
      1
      ·
      1 year ago

      Yes you couldn’t change something so widely used. Look what happened with python 3.

      Fortunately there’s already a tradition among Git users of building a UI on top of the git UI. My project is just a slightly better version of those. It lays a simple sensible interface on top of the chaotic Git interface.