Gut

Dev tools

git cli

SHOW HN2023

314points
181comments
#135of 3,109 in 2023
Top 5%of 2023 by points

How HN took it

DebatedReal support and real criticism

26 positive, 15 neutral or asking, 4 mixed, 32 critical, out of 77 comments about the project. Thread score -0.06.

Idea: 13 for, 19 againstDesign: 8 for, 8 againstPrivacy: 0 for, 3 againstExecution: 0 for, 2 againstDocs: 1 for, 0 against

The thread, comment by comment

Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.

positive neutral or mixed critical about another commenter or something else the maker

What HN said

What people liked

  • Consistent subcommand naming and safety defaults

    From 2 comments
    • > It provides a consistent naming of command. Very nice. > Gut also prevents you from shooting yourself. Excellent. > Finally, git was made when GitHub and others didn’t existed…
      yjftsjthsd-h on HN
    • Pretty awesome. Been using git for 10 years and I trully think its CLI is terrible. It's unintuitive, scary, and opaque. I'll give it a go. Pretty cool for a first year student,…
      iraldir on HN
  • Clean website and documentation

    From 2 comments
    • Regardless of the aim of the particular tool, I just want to say that the visual quality of the web page, documentation, and the quality of the content is excellent and I wish…
      kmarc on HN
    • Will give this a try. I'm a git noob and am intimidated by git, so I'll take a simple interface any day. Also, beautiful web page design.
      replwoacause on HN
  • Useful for beginners and students

    From 2 comments
    • Maybe it's just morning, or maybe I'm a luddite, or both, but my knee-jerk reaction to this was "why does anyone need this? Just learn git." But then I saw the "explain" command,…
      ryukoposting on HN
    • I really like this. I think it takes a beginner to create this too—I know I wouldn't be capable of doing it since I'm just too used to git's terrible UX.
      bin_bash on HN

Objections

  • Opt-out telemetry and unclear data collection

    From 2 comments
    • > It provides a consistent naming of command. Very nice. > Gut also prevents you from shooting yourself. Excellent. > Finally, git was made when GitHub and others didn’t existed…
      yjftsjthsd-h on HN
    • https://github.com/julien040/gut/blob/main/src/telemetry/telemetry.go In that file we find a URL: https://api-events.gut-cli.dev/v1 <-- If data about users is collected here, is…
      1vuio0pswjnm7 on HN
  • Existing git CLIs or GitHub tools make this unnecessary

    From 3 comments
    • Git alternative command line interfaces just make no sense 1. If you want to do something advanced, it will be a lot easier to find help online using regular/original git…
      systems on HN
    • I like that you worked on this but the git cli is already easy to use to be productive. I use the same 5 commands over and over and am happy with that. And Ive met so many people…
      prepend on HN
    • Is git a problem that needs solving? It’s not that difficult to learn/lookup commands.
      kickette on HN
  • Secrets could be committed by gut save

    From 1 comment
    • Secrets management seems like a concern. It's really hard for developers to keep credentials and keys out of git. It looks like `gut save` adds anything that not already in…
      8organicbits on HN
  • Name collides with other gut projects

    From 1 comment
    • I'm starting to get confused with all the git clients/wrapper out there I first thought you would be https://github.com/sdslabs/gut/ or maybe https://github.com/tillberg/gut or…
      BlackLotus89 on HN

Requests

  • Add gut stash

    From 1 comment
    • I feel `gut stash` is sorely missing from the list of commands. It's probably my most used command when iterating on a few ideas to see what works best
      airstrike on HN
  • Show underlying git commands being run

    From 1 comment
    • Congratulations on the launch Julien! My history with git and GitHub is indeed chaotic. It took multiple steps and being explained with different approaches for me to finally…
      pil0u on HN
  • Conventional commits support

    From 1 comment
    • Can you add support for conventional commit[0]? It seems to be a more popular choice than gitmoji. [0]: https://www.conventionalcommits.org/en/v1.0.0/
      maxloh on HN
  • Move branch operations under gut branch

    From 1 comment
    • Looks interesting, thanks for writing and posting. I would suggest you go further and package all the branch related operations as subcommands of "gut branch". For instance, "gut…
      mhalle on HN

Questions

  • What does consistent naming mean relative to git

    From 1 comment
    • How do you define "consistent"? Consistent with what? Because at the moment it looks like it's using completely other terminology than the VCS I am used to.
      ar9av on HN
  • How rebases and forced pushes are handled

    From 1 comment
    • I know you're trying to avoid footguns - but how do you handle workflows where up-to-date rebases are required? Several repos I've been in ask for commits to be rebased to the…
      nidnogg on HN

Alternatives named

  • Gitless

    From 1 comment
    • There is a similar project, Gitless: https://gitless.com/ A maintained fork is here: https://github.com/goldstar611/gitless (I use it)
      relyks on HN
  • bit CLI

    From 1 comment
    • This looks very similar to bit CLI - https://github.com/chriswalz/bit
      chriswalz on HN
  • Magit

    From 1 comment
    • Git alternative command line interfaces just make no sense 1. If you want to do something advanced, it will be a lot easier to find help online using regular/original git…
      systems on HN
  • Lazygit and other git wrappers

    From 1 comment
    • First off, congratulations on entering the Computer Science! Second, I am not sure what is a bigger joke here, the project itself and the OP's innocuous and cute self-promotion…
      nrvn on HN

Category, keywords, summaries and labels on this page were made by AI (Thread Reader v2) and not checked by hand. Each point links to the comments it came from.

Add a badge to your READMEShown on HackerShow
[![Shown on HackerShow](https://hackershow.org/badge.svg)](https://hackershow.org/show/35371469)