07-26-2013, 08:02 PM
(07-26-2013, 07:26 PM)bearbin Wrote: Many new developers are also not very good at SVN so git might be easier.
Are you SERIOUS? Svn is so much easier to grasp than git, it took me about two days to become an svn pro; i'm still struggling with git basics after two years of using it and keep messing up my repo regularly.
Another thing I don't like about git is that there's no way to tell from two revision identifiers, which one is earlier. svn revision numbers are much better suited for this. The nightly build system will be broken, the bug reports will be difficult to read (for the developers), ...
I've heard both a lot of praise and a lot of criticism on the "pull request" feature. In the very least, it makes one person extremely busy with managing all those pulls and merges rather than coding.
Also, is it even possible for multiple people to manage the same repository on GitHub? I don't want to have a separate repository for me and having to sync FakeTruth's or Keyboard's or STR's or anyone else's regular changes.
Git and GitHub, in my opinion, add to the already-too-bad project fragmentation in the open-source realm. Instead of contributing to one master repository, everyone clones and branches their own, so in the end, we have two million linux distributions, a thousand MCServers, ... , each differing from the other by one little change that the branch author wanted to do but couldn't patch in the master. Then when anyone searches for the canonical source of a program, they can't find it; everyone uses different incompatible versions, etc.