16

GIT IS TRASH

WHAT'S THAT, YOU SAY? I'M JUST BEING AN IDIOT WHO ISN'T GOOD AT USING GIT? I DON'T GIVE A CRAP ABOUT YOUR OPINION, I SAY! (eventhoughitstrue). I NEED TO VENT MY ANGER, AND GIT SHALL BE MY VICTIM.

GIT IS TRASH

Comments
  • 11
    Early learning days can be rough. Hang in there!
  • 10
    Do not insult the all-mighty git
  • 5
    Well, use email with an active dev team of 15, let's see how you feel then :/

    Out of interest, how are you using git, terminal or a gui app?
  • 1
    @rusty-hacker Terminal, and a bit of the intellij git integration
  • 14
    Did you loose your "head"? :P
  • 4
    @DavidINC personally, I use an app in most cases, source tree or git kraken if on linux.

    The gui makes it easier to figure out who's done what, what branch I'm on, handle merge conflicts, tags, rebase, file specific history logs ...

    Sometimes I cannot find specific functionality like editing a commit in the gui, then I use the terminal.

    Would suggest using a dedicate gui app for a bit, you might find it much easier than terminal or intellij's builtin functionality.
  • 2
    @rusty-hacker question: is there something that cli, gitk, and fugitive vim can't do in an easy and fast way?... Just wondering because I've never felt I need an app like source tree or git kraken. Thanks in advance :)
  • 5
    Git makes your life as a dev a lot easier than you might realize. I haven't seen any other system that is so broadly forgiving to huge fuck-ups like git. Yiu can revert, jump back and forth and pretty much cherry pick every little change as you please.
    It allows for easy versioning, easy collaborative work and reliable backup.
    You can always have a detailed history of your changes and everything you have committed.

    I suggest you take a deeper look at the git cli and how git exactly works.
    Git is a tool that becomes ever more powerful and faster with experience.
  • 1
    I feel you bro. Been there!
    Loving it now
  • 4
    @voodoo14 nice to see a fellow vim user. Those cli tools will never let you down.

    Personally, I am a power terminal and nvim user. I hate to admit it, but when it comes to source control, because of better visual aids, I find the gui apps get my work done quicker and with less hassles.

    Small things like seeing and easily ticking which files to commit also helps, rather than typing multiple file names ... (usually have specific things I want to commit with different messages)
  • 1
    I'm a designer and get better along with www.gitkraken.com than using git with the terminal.
  • 1
    The first time I used git I accidentally deleted all the code in the project. 🙁
  • 0
    @KylePiira rest in pepperoni
  • 2
    I'm learning git, and it sucks, but I know it'll benefit me in the long run. Plus I can host my personal website on it.
  • 3
    @TheDevil it sucks because you don't know it? Then 99% of things suck because you don't know them
  • 1
    Here's a ++. Now please go back and study Git ;)
  • 0
    He is actually right. git *is* indeed trash. For those that started coding less than like four years ago: version control has not always been written by egomanic kernel hackers that don't care for usability and like solving their own little problems without caring how that affects millions of others. There have been tools that seemed complex at that time, but look easy as pie compared to git. git just became popular because GitHub & Co have built an amazing system on top of a piece of unusable shit.
  • 0
    I'd maybe respect this post if it was a haiku
  • 3
    Try Google drive
  • 1
    Git as a concept is amazing, and the cheap branching enabled by the way it works is a game changer. (not that it does anything unique, or even really new, but it made it mainstream)

    Git itself, though, is a mess. Wildly inconsistent, dangerous, and easy to screw up.
  • 1
    @DrEmann excuse me... What?
  • 3
    @voodoo14 Something that's way easier to do in GUI than CLI is selecting which lines of which files to commit.

    I'm doing that a lot on Github GUI app, it helps if you worked on several things at the same time and want to break it down to several commits.

    There are a lot of things you can't do in the GUI though. That's why you need to know your way around CLI too.
  • 1
    @Fradow Though I haven't used git add -p that much I was wondering about using other apps different from gitk, git-gui. PD: You can also patch with git-gui.
  • 1
    @voodoo14 I didn't even knew the name since I never used it in CLI. After having a look at the doc, there are situations where you can't actually achieve some commits you would do with a GUI, because git add -p works with "hunks" and not line by line. I didn't find a way to select specific lines inside a hunk when reading the doc.

    For the record, I use Github for Desktop on Mac (I'm not sure the Windows/Linux version work as well, I remember issues when I had to use it on Windows).

    Just because it's from Github doesn't mean you can't use it for non-Github repo. It just means you can't use some features which are Github specific. I still use the app when commiting for other remotes (Heroku, and an internal repo for example).
  • 0
    @Fradow thank you. There are a lot of options while git add -p.

    s - split the current hunk into smaller hunks.

    So you can split it over and over. Not sure if that's what you're talking about.
  • 0
    @TheDevil @daniel-kun
    Wat?

    If git is so terrible, then make a better version control system that runs more efficiently than git.
    Otherwise y'all are just useless critics bitching about something amazing cause you have a falsely elevated sense of superiority.
Add Comment