It could use neural network for this for all I care. Anything but merging lines as if they contained completely meaningless string of characters.
Things I hate about Git (2012)
41–50 of 83 posts
Re: Things I hate about Git (2012)
#42"it's complicated": yes,it is. it's a product designed and built for people who deal with complex systems and information models on a daily basis; they're the equivalent of a professional pilot... not your feeble, senile grandmother. You wouldn't buy your feeble senile grandmother a 787, chuck her in with no training and simple expect her to fly to Bali, would you? "I don't like it and here's a heap of examples which…
There are two categories of possible criticisms: the model, and the implementation. Fixing the implementation means changing code, improving APIs (e.g. local/remote branch delete). Fixing the model means finding an everything different system. Yes, a graph-based VCS more complicated than a linear one. But it also matches realities of collaborative software development. And reality is complicated. As you might guess,…
My problem is implementation.
Re: Things I hate about Git (2012)
#43Earlier quoted context omitted.
Is hg easier to use? Or any other DVCS not created by such a bad UX practitioner?
For simple workflows (and certainly for beginners), hg is far easier to use than git. However when it comes to advanced usage, I personally find git more intuitive and frankly more powerful. Granted, I learned git first and had been using it for 6 years before using hg.
Re: Things I hate about Git (2012)
#44Re: Things I hate about Git (2012)
#45I mean, it already does everything under the sun, so there's a challenge for anyone up for it!
Re: Things I hate about Git (2012)
#46The man pages are one almighty “fuck you”. And there are people I've wanted to strangle for telling me: RTFM. The examples in this article are the crowning example of why their painful death would be well-deserved. There's this thing about bedside manner that technically adept people need to cultivate, just as doctors do. Did I mention I despise cold, snotty doctors too? There's nothing worse than a condescending pri…
The best thing in your comment is this sentence:
There's this thing about bedside manner that technically adept people need to cultivate, just as doctors do.
That's a well-put sentence, plus, I feel like you're on to something. I feel the same way, incidentally. I don't think it's productive or collegial to tell someone to "RTFM" or "use Google". If you're struggling with something right in that moment, the best thing to do is show some kindness and empathy and sit down and help. Then, once the problem is resolved, that's the moment where you can "teach a man to fish".
You seem like you have a talent for writing and your vocabulary and prose are quite good - just rework the tone and omit the profanity and you'll see some upvotes.
Re: Things I hate about Git (2012)
#47Git is pretty difficult to learn, but the customizations it allows are amazing. To get a "fancy oneline log" output, add the following to your `~/.gitconfig` [alias] ll = log --graph --oneline --decorate --date=short --all --pretty=format:'%ad %h %Cgreen%an %Cred%d %Creset%s' then run git ll It's great when rebasing your way out of spaghetti-commitlog situations.
I personally have this in my ~/.config/git/config:
[alias]
lg = log --graph --pretty=format:'%C(auto)%h%d %s %Cgreen(%ar) %C(bold blue)%Creset'Re: Things I hate about Git (2012)
#48Re: Things I hate about Git (2012)
#49Once you get the essence of git (objects, graph, commits as snapshots etc) everything becomes really easy. You don't need to memorize all command just need to understand some basic concepts. And some points about the article. Git is a framework actually, you need some workflow to use it in a team. So git requires a lot of discipline from all team members. You can't just "commit" as in subversion, you must understand…
That said, the command line UI really is infuriating - checkout means 3 different things depending on what the argument is, it's never clear to me whether I should be using "origin master" or "origin/master," etc. I'm also not entirely sold on the usefulness of the index, but perhaps that's cause I'm still new to using git.
Re: Things I hate about Git (2012)
#50I'd like git to be aware of the grammar of the files it's diffing and merging. It could use neural network for this for all I care. Anything but merging lines as if they contained completely meaningless string of characters.