[โ€“] 1 point 4 months ago

Yeah also people get into a mess and don't understand the state of the repo. Like they're organising files without ever running ls. If you ask these CLI fanatics for the solution they'll say "you don't need a GUI, just run git log --tree --oneline --decorate --all"... which is just a poor man's GUI.

  • source
  • parent
  • context
  • [โ€“] 1 point 4 months ago

    Well I disagree. If you create a popular project, and then are a complete dick about reasonable requests, then that seems like an immoral thing to do to me.

    Of course you're allowed to say "sorry I don't have time to work on this any more", or "I don't think this feature belongs in this project" or whatever. Totally fine. But there are still behaviours that IMO are not ok. For example if Homebrew decided to inject donation request code into every package it installs. Or if ffmpeg added code that detected porn and refused to decode it.

    "BuT iTs FrEe! They can legally do what they like!" Sure, but it still makes them a dick.

  • source
  • parent
  • context
  • [โ€“] 15 points 4 months ago (3 children)

    That's a lot of words. I think the reasons are pretty simple:

    1. Some people just don't care.
    2. The Git CLI is poorly designed e.g. the many different ways to delete something.
    3. Some Git concepts are very poorly named, e.g. the "index", "ours/theirs". This adds to the confusion.
    4. There are many Git GUIs but only a very small number of actually decent ones (if you're wondering: GitX, SourceGit, Git Extensions, and the Git Graph VSCode extension).
    5. There are a lot of idiots out there telling people not to use Git GUIs, when they are clearly the best way to learn how to use Git. Its easy to get into a mess if you can't see what you're doing.
    6. Git isn't actually as simple as us pros would like to think. The underlying model and even the implementation isn't too complex (I've written a Git client form scratch; not too hard apart from the lack of specs/docs). But you can easily get into a state where you're pulling from a remote and someone else has pushed to the same branch so you need to resolve that (oh btw don't do what Git tells you to!), and maybe it involves submodules too, and you basically need to fully understand Git's model and be pretty good at the awful CLI too to resolve it.
  • source
  • [โ€“] 1 point 4 months ago (2 children)

    What arbitrary line of popularity suddenly requires me to support every use-case, by never breaking something in a project nobody is paying me to build?

    Not what I said at all.

    FOSS maintainers owe you NOTHING. Nada. Zip.

    Oh so it's either "nothing. Nada. Zip." or "support every use-case". Nice false dichotomy you've got there.

  • source
  • parent
  • context
  • [โ€“] 1 point 4 months ago (4 children)

    I disagree. If you make a project, put it out there for.people to use, and it becomes popular, you have some moral obligation not to dick over people who have come to depend on you. I'm not saying you have a moral obligation to e.g. provide free support forever or work weekends or whatever.

    You can think otherwise but IMO that makes you a bit of a dick.

  • source
  • parent
  • context
  • [โ€“] 4 points 4 months ago*

    Freaking finally. (Well when it's actually released anyway.) Kind of crazy how long this super obvious feature has been ignored by all the forges. (Except Tangled, but that has other issues.)

    Also this is going to be a big differentiator compared to Gitlab or Forgejo.

  • source
  • view more: โ€น prev next โ€บ