1. 19
  1.  

  2. 20

    Looks nice! Too bad that it seems to be OS X only and not free software, but otherwise, nice. Though I’m a CLI junkie so I don’t think I would use it anyway.

    1. 2

      Wish it were cross-platform… maybe a clone can be made with D3.js?

      1. 5

        You mean a native web-app using something like nw.js?

        That’d be nice to look at, but to have to download 50MB just for a Git visualizer… meh. I’m gonna stick to my tig.

        1. 1

          Hmm, that looks nice. I am surprised I haven’t seen this before, I usually just use gitg to visualize the tree.

    2. 19

      Mac only and not free software :-(

      1. 2

        What did this add to the conversation?

        1. 9

          I think of my comment as like a seed, or a droplet of water. Putting the ideas of cross platform free software as a nagging nugget in the back of the reader’s mind. This software seems pretty great and it is too bad it isn’t cross platform and free software.

          I don’t see anything on the website to suggest it couldn’t be otherwise.

          If you look at the other comments, they have a similar sentiment. In the small it adds nothing, but as a group of comments, it is revealing. And as users of software, we should demand these things, even if it is a pain in the ass to developers.

          I try my best not to be a hypocrite. My own software that I publish should be held to the same standards, and I try. It is a major pain in the ass, but I try.

          EDIT:

          This can add to the conversation

          http://forums.gitup.co/t/cross-platform-support/134

          Why are developers doing a poor job of engineering these things to be so locked down and hard to change?

          1. [Comment removed by author]

            1. 7

              People have been asking for Free software since long, long before app stores existed. That’s how we got GNU. It’s not “the app store mentality”, it’s “the four freedoms”.

              The author is free to write non-Free software, and users are free to express their disappointment at the author’s choice.

              1. [Comment removed by author]

                1. 3

                  Sorry for the confusion. I think you were the only one to think that I meant free as in beer. I’ll make sure to capitalize ‘free’ in the future.

              2. 1

                hdevalence summed it up nicely below. I want to add that I think you may actually like the ideas behind Free Software (Free as in Freedom, not Free as in beer). It is as far from the App Store mentality as you can get.

                The four freedoms are:

                1. Free to run the software as you wish.
                2. Free to study how the program works and change it.
                3. Free to share the program with others.
                4. Free to share the modified version with others.

                You can read more here

                | That’s one hell of a presumptuous statement. Clearly we can’t all be as good as you.

                I would not pick on a inexperienced developer like that. But can you argue that the developer of GitUp is inexperienced? Seems he is pretty good and should know better. Also, he wrote some open source libraries and my guess is that he is planning on selling GitUp (nothing wrong with selling). Maybe he made it Mac only because he knows Mac people have deeper pockets? Though it seems most GUI apps he wrote are Mac only.

                1. [Comment removed by author]

                  1. 0

                    I didn’t say it out of context. I said it because there was a ticket asking if gitup will be cross platform. The developer basically said, not for a while because the design uses object C too deeply, which makes it harder to port. He didn’t reject the idea of cross platform support.

                    In other words, he didn’t think too far ahead.

        2. 4

          This looks great! I especially like the tree visualization and manipulation. So many things become easier once you can “see the tree”.

          I’ve settled on a workflow that combines command line for quick commits and work in progress. Then I load up Gitx (rowanj fork: https://rowanj.github.io/gitx/) and do interactive rebase or something and edit the commits one by one with good messages and add/remove chunks in the staging interface. I’ve tried a few times to get the hang of staging chunks via command line but while I understand it’s possible and fully supported, a visual UI works wonders and saves me a lot of time.

          1. 6

            So many things become easier once you can “see the tree”.

            When teaching hg, I always tell people to alias hg log -G to hg glog, and I make a point of always telling them to use hg glog. It does seem to help. Our Windows hg users by and large use hg through TortoiseHg, which also has the DAG front and centre. I really don’t get why git users seem to have a habit of not really thinking about the DAG. The average git user thinks about branches, but cares little about their topology.

            Remember that most VCS users don’t really want a VCS at all. Most, not the kind that posts to lobste.rs or HN, just consider babysitting history to be a chore, and hardly ever learn anything beyond four or five commands. Their method for getting out of trouble is to re-clone, or follow a convoluted path to get back to a state that they know what’s happening instead of trying to learn new ways around the state they’ve found themselves in. There is Google-backed usability research to back this up.

            1. 2

              git reset --hard all the things~

            2. 3

              i like git-cola for interactive rebases and the venerable gitk for exploring the graph

            3. 2

              Worst icon ever.

              1. 2

                I can’t think of anyone who would disagree.