3 ms·
From my experience, most people issues with git is because they do not really understand how it works (or try to apply what they've seen with other cvs). Now I
by mrchlblng 12y ago
From my experience, most people issues with git is because they do not really understand how it works (or try to apply what they've seen with other cvs).
Now I agree that having to understand internals might be seen as an engineering failure, however
* internals are pretty quick to cover
* for students learning software development, I thought it would be interesting to see that you can have very few low-level objects that offer powerful high-level actions
- privong 12y agoI can see where those things would be interesting for students learning software development, but not everyone who uses git is doing that type of development. To be fair, I am coming at this from the standpoint of someone who uses git for science, rather than software development. Yes, I use it to track changes in code, but vast majority of that code is scripting analysis procedures (so knowing about internal data structures does not directly help me do my job). I also use git to track changes in LaTeX manuscripts. So, while your first point is arguably universally applicable (that knowing the internals would help me use git), the second point does not apply to everyone. I am not suggesting that all tutorials should jettison an early discussion of the git internals, but merely suggesting that including such a discussion early on, may not be appropriate for some audiences.
- bch 12y ago> To be fair, I am coming at this from the standpoint of someone who uses git for science, rather than software development As a software developer, I would rather spend my time on the task at hand (my own development) rather than git internals. I don't understand why so many people apologize for the (imo) poor user-experience that git provides...