6 ms·

you need to read "Git for dummies"

kansface 14y ago
git has no user interface. git expects its users to have an in depth understanding of its implementation details. These are failures of git. Ideally, studying abstruse man pages to avert disaster wouldn't be required of new users.
- abimaelmartell 14y ago
  i been using git for almost two years, never needed a gui
  - deleted 14y ago
    [deleted]
- jhaglund 14y ago
  Git doesn't have much of a user interface because it's target is developers who want to use the command line. Git is confusing until it's not, and then it's awesome. It's kinda like you're using wget to surf the web, and complaining that it doesn't have a GUI. http://git-scm.com/downloads/guis http://git-scm.com/downloads/guis
  - niggler 14y ago
    GUI != UI parent comment is arguing that the command-line interface is nontrivial, which is a fair criticism. Contrast with 'cp' or 'mv'
    - tingletech 14y ago
      To use wget, I often need to read the manual or look up some notes to get the exact command I want.
    - jhaglund 14y ago
      Well, go right ahead and use cp and mv for your source control! No one (except maybe linus) ever said git is easy. But it is flexible and powerful. Anyway, this whole thing comes down to the user ignoring clear warnings. It seems clear to me that using "force" can break things.
- kh_hk 14y ago
  You are confusing 'implementation details' with how does git abstract reality. You are not supposed to know how things are implemented, really.
- Rarebox 14y ago
  Git interface is hard, because git is hard. Git is hard because it is so powerful. Git developers don't care about newbie users who can't even bother to RTFM. There is just no reason they should. Git user interface is fine when you finally learn how to use git.
  - LeonidasXIV 14y ago
    A browser is hard. Firefox is easy. I don't think your reasoning holds. That's why we have abstractions, to make hard things easy.
    - Rarebox 14y ago
      The idea of a browser is far easier to understand than git from users perspective. Implementation is something user doesn't have to know about (for firefox or git). What makes git so powerful is that it doesn't abstract things as much as other systems. To make git easier would mean making it less powerful. I rather use a tool that is complex than a tool that doesn't let me do what I want.
  - lennartregebro 14y ago
    No, git is not hard because it's powerful. It's hard because it's defaults are non-sensical, and it's user interface are neither close enough to how it's internal mechanics to be predictable, but not far enough from the internal mechanics to provide understandable abstractions. The result is that it behaves unpredictably and confusingly. And that's a bad UI, no matter how powerful things are below. "Git developers don't care about newbie users who can't even bother to RTFM." This is probably true. "There is just no reason they should." Yes there is.

git has no user interface. git expects its users to have an in depth understanding of its implementation details. These are failures of git. Ideally, studying abstruse man pages to avert disaster wouldn't be required of new users.

abimaelmartell 14y ago
i been using git for almost two years, never needed a gui
- deleted 14y ago
  [deleted]
jhaglund 14y ago
Git doesn't have much of a user interface because it's target is developers who want to use the command line. Git is confusing until it's not, and then it's awesome. It's kinda like you're using wget to surf the web, and complaining that it doesn't have a GUI. http://git-scm.com/downloads/guis http://git-scm.com/downloads/guis
- niggler 14y ago
  GUI != UI parent comment is arguing that the command-line interface is nontrivial, which is a fair criticism. Contrast with 'cp' or 'mv'
  - tingletech 14y ago
    To use wget, I often need to read the manual or look up some notes to get the exact command I want.
  - jhaglund 14y ago
    Well, go right ahead and use cp and mv for your source control! No one (except maybe linus) ever said git is easy. But it is flexible and powerful. Anyway, this whole thing comes down to the user ignoring clear warnings. It seems clear to me that using "force" can break things.
kh_hk 14y ago
You are confusing 'implementation details' with how does git abstract reality. You are not supposed to know how things are implemented, really.
Rarebox 14y ago
Git interface is hard, because git is hard. Git is hard because it is so powerful. Git developers don't care about newbie users who can't even bother to RTFM. There is just no reason they should. Git user interface is fine when you finally learn how to use git.
- LeonidasXIV 14y ago
  A browser is hard. Firefox is easy. I don't think your reasoning holds. That's why we have abstractions, to make hard things easy.
  - Rarebox 14y ago
    The idea of a browser is far easier to understand than git from users perspective. Implementation is something user doesn't have to know about (for firefox or git). What makes git so powerful is that it doesn't abstract things as much as other systems. To make git easier would mean making it less powerful. I rather use a tool that is complex than a tool that doesn't let me do what I want.
- lennartregebro 14y ago
  No, git is not hard because it's powerful. It's hard because it's defaults are non-sensical, and it's user interface are neither close enough to how it's internal mechanics to be predictable, but not far enough from the internal mechanics to provide understandable abstractions. The result is that it behaves unpredictably and confusingly. And that's a bad UI, no matter how powerful things are below. "Git developers don't care about newbie users who can't even bother to RTFM." This is probably true. "There is just no reason they should." Yes there is.