Re:The Fossil distributed version control system
by buvanshak on Sunday April 15, 2018 @01:27AM
(#16841380)
> Use a Git GUI like SourceTree..
It quickly fails to scale. The issue is when you want to use commands to find the successors and build some processing over it..
>"The mental model for Git is needlessly complex" - Again, a Git GUI can make it really easy to keep track of "changed but not ready to commit..
That is a very limited situtation. In the course of using a VCS, for a long running project, one encounters numerous situtations where having a complex mental modal quickly feels exhausting...
> The exact same thing is available in Git via "git log --graph --all --decorate" or a GUI that shows the graph.
No. it is a bit different. In Git, branches can easily jump around, and the commits that were previously under a branch will have no information in them regarding which branch they were originally made..
>. Again, there is tooling available for Git to remove this requirement.
Again, you are not thinking like a power user. GUI's only works if you follow some predefined "happy path"..
> I'm just saying that his arguments here show a lack of knowledge about the available tooling for Git
To me, it seems that you are lacking enough experience to identify what the author is talking about..
It quickly fails to scale. The issue is when you want to use commands to find the successors and build some processing over it..
>"The mental model for Git is needlessly complex" - Again, a Git GUI can make it really easy to keep track of "changed but not ready to commit..
That is a very limited situtation. In the course of using a VCS, for a long running project, one encounters numerous situtations where having a complex mental modal quickly feels exhausting...
> The exact same thing is available in Git via "git log --graph --all --decorate" or a GUI that shows the graph.
No. it is a bit different. In Git, branches can easily jump around, and the commits that were previously under a branch will have no information in them regarding which branch they were originally made..
>. Again, there is tooling available for Git to remove this requirement.
Again, you are not thinking like a power user. GUI's only works if you follow some predefined "happy path"..
> I'm just saying that his arguments here show a lack of knowledge about the available tooling for Git
To me, it seems that you are lacking enough experience to identify what the author is talking about..