Conversation

Notices

1. nixCraft 🐧 (nixcraft@mastodon.social)'s status on Wednesday, 18-Sep-2024 02:01:40 JST nixCraft 🐧

   Git showdown! CLI or GUI? Which interface do you favor for your Git workflow and why? ⚔️💻

   • Alex, just zis guy, you know? (alexmorse@mastodon.social)'s status on Wednesday, 18-Sep-2024 02:06:25 JST Alex, just zis guy, you know?

     in reply to

     @nixCraft CLI

     I can type and autocomplete filenames faster than I can navigate through a directory tree in a gui. It does all the things.

   • RyanParsley (ryanparsley@mastodon.social)'s status on Wednesday, 18-Sep-2024 02:08:43 JST RyanParsley

     in reply to

     @nixCraft if I was king of git, everyone would start with the CLI until they understood it and could articulate a reason they needed a richer interface.

     Starting with the GUI seems to prevent people from understanding some fundamentals that they'd be better off understanding sooner rather than later.

   • R (foo__@mastodon.social)'s status on Wednesday, 18-Sep-2024 02:10:05 JST R

     in reply to

     @nixCraft CLI, I've proper manners

   • Joseph Dickson (josephdickson@mastodon.social)'s status on Wednesday, 18-Sep-2024 02:15:57 JST Joseph Dickson

     in reply to

     @nixCraft when I Git, I CLI.

   • BigLinter (biglinter@mastodon.social)'s status on Wednesday, 18-Sep-2024 02:26:06 JST BigLinter

     in reply to

     @nixCraft cli

   • Freevolt (freevolt24@mastodon.social)'s status on Wednesday, 18-Sep-2024 02:57:22 JST Freevolt

     in reply to

     @nixCraft Is there any person using git in one way only..?

   • David Skuza (dskuza@mastodon.social)'s status on Wednesday, 18-Sep-2024 03:49:41 JST David Skuza

     in reply to

     @nixCraft lazygit

   • hansvschoot (hansvschoot@mastodon.social)'s status on Wednesday, 18-Sep-2024 05:36:46 JST hansvschoot

     in reply to

     @nixCraft svn all the way!

   • ploppy (ploppy@mastodon.social)'s status on Wednesday, 18-Sep-2024 06:30:27 JST ploppy

     in reply to

     @nixCraft TUI (tig) for browsing the history, CLI for everything else. I'm on the terminal anyway. No need to switch to a GUI that does not work when working on another machine remotely. (I know there are ways. But it’s overhead with no benefit.)

   • lemgandi (lemgandi@mastodon.social)'s status on Wednesday, 18-Sep-2024 09:44:08 JST lemgandi

     in reply to

     @nixCraft CLI all the way. I had coworkers who used the GUI, and they were always struggling to correct commit or push errors. Hiding the commands behind an opaque GUI turned out to be a poor choice.

   • deltarays (deltarays@mastodon.social)'s status on Wednesday, 18-Sep-2024 17:27:15 JST deltarays

     in reply to

     @nixCraft CLI, and I usually have a dedicated terminal tab open where I only need to go up by a couple of commands to find the correct one.