Gitless: a version control system • Hacker News Board

Re: Gitless: a version control system

#121

Post by rplst8 » Sun, Oct 02, 2016, 3:52 PM UTC

vbtemp wrote: post #108

k__ wrote: post #102

Git is, like many professional tools, something you simply got to learn. But like with many professinal tools, you don't need to know everything to get to work. I don't know all Photoshop or Ableton Live features, but I can improve my photos or create songs non the less. With these commands you can already start your own repo and work on it locally: git init // crate new repo git status // show which files are change…

> Git is, like many professional tools, something you simply got to learn. Nailed it.

Agreed. I'm seeing terms like "elitist" being thrown around below for "git apologists" when it's simply a matter of learning a tool. Not everyone needs all the power of the git CLI and the complications it brings - but when you do need it, it's there to fix the dumb things we all do sometimes.

I think if you look deep in the guts of Clearcase for example you will see nastiness that makes git look like the ls command.

Re: Gitless: a version control system

#122

Post by [deleted] » Sun, Oct 02, 2016, 3:54 PM UTC

KKKKkkkk1 wrote: post #112

heisenbit wrote: post #65

Git is powerful. While the underlying architecture has beautifully simple aspects arguing that the complexity of the git tool-chain is simple is similar to arguing that TeX is simple as it is written in a simple language. Git is managing trees of file-sets in a distributed manner. It took many generations of configuration management systems to get there. Git is bottom up. Understand the inner workings and you know wh…

As a tangent, I think calling git a distributed system is misleading. Git is primarily a history manager for a local directory tree that has commands to sync with remote machines. Having to type stuff like git remote add mothership ssh://foo@bar.baz git push mothership in order to sync is not what I usually associate with a distributed system. The word distributed conjures something that's more like dropbox, where th…

[deleted]

Re: Gitless: a version control system

#123

Post by zajd » Sun, Oct 02, 2016, 3:55 PM UTC

fail2fail2ban wrote: post #117

zajd wrote: post #111

Earlier quoted context omitted.

Here in the real world if you fuck up your local repo by running commands you don't understand there isn't a "git expert" to come by and fix it for you, in the same way if you make a VM and fuck up your local machine there isn't going to be a "linux expert" to come in and explain how to fix what you did wrong. Part of the benefit of the tool is that you can blow everything away and restart. It's distributed, which me…

Your points would be more salient if you could make them without falling back on profanity.

They'd also be more salient if I didn't have to make them 10 times in a thread because everyone feels like their opinion on how "git is too hard" is worth sharing. It gets tiring defending git from the uneducated masses and hearing the same stuff trotted out over and over again that has no value whatsoever.

Re: Gitless: a version control system

#124

Post by matt4077 » Sun, Oct 02, 2016, 3:57 PM UTC

k__ wrote: post #102

Git is, like many professional tools, something you simply got to learn. But like with many professinal tools, you don't need to know everything to get to work. I don't know all Photoshop or Ableton Live features, but I can improve my photos or create songs non the less. With these commands you can already start your own repo and work on it locally: git init // crate new repo git status // show which files are change…

This is very close to the result of the study that was I believe he reason to write gitless:

- Most people use git by learning a set of a few commands

- A minority actually understands git on a deeper level

But both groups form a mental model of how git works, and that model is apparently usually wrong, which results in those cases were you get stuck and just start with a fresh checkout and manually reapplying the changes you wanted to commit.

Re: Gitless: a version control system

#125

Post by [deleted] » Sun, Oct 02, 2016, 3:57 PM UTC

KKKKkkkk1 wrote: post #112

heisenbit wrote: post #65

Git is powerful. While the underlying architecture has beautifully simple aspects arguing that the complexity of the git tool-chain is simple is similar to arguing that TeX is simple as it is written in a simple language. Git is managing trees of file-sets in a distributed manner. It took many generations of configuration management systems to get there. Git is bottom up. Understand the inner workings and you know wh…

As a tangent, I think calling git a distributed system is misleading. Git is primarily a history manager for a local directory tree that has commands to sync with remote machines. Having to type stuff like git remote add mothership ssh://foo@bar.baz git push mothership in order to sync is not what I usually associate with a distributed system. The word distributed conjures something that's more like dropbox, where th…

[deleted]

Re: Gitless: a version control system

#126

Post by twic » Sun, Oct 02, 2016, 4:00 PM UTC

gcb0 wrote: post #79

m3kw9 wrote: post #43

Earlier quoted context omitted.

Just use the normal git fallback command

me nor my web search engine never heard of it

Perhaps m3kw9 means that if there's something that you can't do in Gitless, you can fall back to the Git way of doing it, since both use the Git plumbing.

Re: Gitless: a version control system

#127

Post by arielb1 » Sun, Oct 02, 2016, 4:00 PM UTC

bluejekyll wrote: post #42

rplst8 wrote: post #28

When people say they don't like git, I lose a little faith in them as a programmer and/or engineer. This is probably due to my own biases of having worked with folks that just don't want to invest the time in learning it. That or they are afraid of branching/merging. To me this indicates intellectual laziness which isn't the kind of laziness that makes a good programmer (as is with the quote from Larry Wall and the k…

I use git all the time and prefer it for all types of workflow as a VCS, but this idea that git is perfect and it's your own fault for not learning it properly is ridiculous. UX/UI in programs is important. I believe that git has one of the worst, most inconsistent UX's of all time. You can see this by the fractured commands. Quick examples: 'git reset' vs. 'git revert' and sometime 'git checkout' 'git checkout' vs.…

How are `git reset` and `git revert` related? How are `git fetch` and `git cherrypick` related?

Re: Gitless: a version control system

#128

Post by twic » Sun, Oct 02, 2016, 4:02 PM UTC

leshow wrote: post #94

wreft wrote: post #70

Earlier quoted context omitted.

I don't think perjudicial is a word.

you are wrong

It seems to be a word in Spanish. It isn't a word in English.

Re: Gitless: a version control system

#129

Post by dahart » Sun, Oct 02, 2016, 4:03 PM UTC

douche wrote: post #118

dahart wrote: post #109

My criteria for whether an interface to git is truly easier is whether artists can use it. I've worked in games alongside artists, with everyone using Perforce. At some point we switched to Perforce for the art, and git for the programmers, with a big janky glue system in-between. Git couldn't really handle all the binary assets, and the artists couldn't really handle git, so it made sense. When we switched, it also…

As far as version-controlling art, I'd lean towards a system where checking a file out locks it from any other concurrent modifications. Unfortunately, trying to merge concurrent changes into an image file, for instance, is just about impossible. It's almost as bad trying to work with MS Office file types - I wish I could get people on my team to use something else that is more VCS friendly, like HTML or Markdown, bu…

Yeah, exactly. Perforce has file locking, and the need to file-lock binary assets is a great example of why a central server setup has advantages over a DVCS in some cases.

The alternative to file locking could be a rule set for who or which branches win when there are conflicts in binary data. Then again, as an artists you would rather know if someone's touching an asset before you dig in. With art & binary assets, it's more important than with mergeable code that your team and work is properly organized in a way that avoids multiple people touching the same file.

Re: Gitless: a version control system

#130

Post by musicnarcoman » Sun, Oct 02, 2016, 4:04 PM UTC

kasey_junk wrote: post #37

rplst8 wrote: post #28

When people say they don't like git, I lose a little faith in them as a programmer and/or engineer. This is probably due to my own biases of having worked with folks that just don't want to invest the time in learning it. That or they are afraid of branching/merging. To me this indicates intellectual laziness which isn't the kind of laziness that makes a good programmer (as is with the quote from Larry Wall and the k…

When people suggest that git is great I lose a little faith in them as a programmer cause it indicates to me they don't have much breadth if experience with source control systems & they are too intellectually lazy to investigate alternatives. Could just be my biases I guess.

So, what alternatives are you suggesting?

I have tried and used Mercurial, SVN, RCS, CVS, Bitkeeper, TFS, Bazaar, Perforce, Darcs and of course Git. Granted, Git may not be great, but it is still my first choice.