Build Git – Learn Git

41–42 of 42 posts

Re: Build Git – Learn Git

#41

Post by codez » Tue, Jan 21, 2014, 3:42 PM UTC

andrewaylett wrote: post #39

codez wrote: post #37

It's a cool concept but like other comments say it overlooks a lot of the things that make git, git. Best way to learn? use it! Maybe just create a dummy repo and go from there with it. Maybe use the GUI tools until you're comfortable with the command line. For me personally, it was command line first. If you aren't sure about something with git, googling it will pretty much always throw out your answer.

I'm not sure I quite agree. Use it, yes, but if you're using Git as a black box then you're much more likely to be frustrated by it than if you understand what's going on under the hood. I tend to point people at "Git from the bottom up"[0] -- it gives people the understanding they need to work out the effect they require, from which they can work out which set of commands will get them there. [0] http://ftp.newartis…

Most people will not be using advanced functions though and if people generally understand how version control works, I don't think git is super hard to pick up and learning whilst doing is most effective for me.

I'm sure most people are probably aware of : http://try.github.io/

which is a cool little resource for learning git.

Re: Build Git – Learn Git

#42

Post by chromejs10 » Tue, Jan 21, 2014, 5:48 PM UTC

chinchang wrote: post #38

chromejs10 wrote: post #36

Earlier quoted context omitted.

I 100% agree. It's always great to try to implement complicated things, but it misses the point if what you're implementing is nothing like the original system. You aren't learning how Git works if you do it that way are instead just mimicking API names

Reiterating on my point again, the aim of this project is not to replicate Git. JS-Git ( https://github.com/creationix/js-git ) does that.Here I am trying to code basic concepts relaxing complex stuff so that reader can focus & visualize more abstract concepts. I have tried to bring in concepts as and when wanted instead of just overloading the reader with complex stuff all at once.

Which is fine. But you're specifically saying that you are building Git to learn how it works. All I'm saying is, based on your wording, you need a disclaimer that this is not how Git works internally. You can already get the gist from a lot of the comments that they think they now know how Git works after reading this post.

I appreciate the effort and think it's a great idea to implement something your own way, I'm just trying to point out that you're saying this is how THE Git works, which it isn't. Nice write up as a whole though

Post reply on HN