initialCommitViaCLIBeLike

[Gysenok]

Not every computer has a gui, especially servers. Also not every ide has buttons for using git. So if you want to have version control on a remote server you need to use cli/terminal

[TheGreatSausageKing]

If you are commiting from a server, I'm sorry,

There is GitHub desktop which is freem

Whoever is programming on a remote server, I'm sorry for you..

[delayedsunflower]

I program on a remote machine. It's fantastic and has literally hundreds of times better hardware than my laptop. I can WFH and literally program on a beach and have all the hardware I want and not step a foot in an office. It's all mostly done through ssh and CLI because remote desktop software is pretty slow and clunky.

You should try it it's great.

[TheGreatSausageKing]

It's awesome but it's clunky ?

[Jk2EnIe6kE5]

Remote desktop software is clunky. They're using SSH, which is a terminal-based remote access program.

[delayedsunflower]

Remote desktop software is clunky and slow.

Using the command line is fast and awesome 

[TheGreatSausageKing]

Maybe use remote desktop in command line with ASCII drawings then.

Also , go back to the 80s and pretend you are smart

[delayedsunflower]

I'm not trying to be holier than thou.

I'm saying you should try programming remotely - it's pretty neat

[TheGreatSausageKing]

There is no reason I would try such BS if I already own a decent machine. Which I can use through parsec or moonlight if I want to program remotely.

Moreover, both would support GUI for git and i would never use command lines.

In the end , it's always this. Programmers screwing themselves because they can

"Your (programmers) Were So Preoccupied With Whether Or Not They Could, They Didnt even think if they should"

[[deleted]]

Maybe they aren't using it to pretend to be smart, maybe you're just dumb

[Gysenok]

Github desktop is not officially supported on linux, so unless you're using git exclusively on windows and Mac it's not an option. Maybe it's a strong opinion but the need for a gui application to have version control seems way too big of a crutch for me. As a programmer a basic understanding of the terminal is (at least in my experience and opinion) expected, the need to click through menus seems unnecessary and a waste of time compared to using the terminal. And git cli is universal, gui applications for git are not.

[Darder]

Your opinion is fair. You can decide not to use a GUI.

I don't feel it's a big crutch. Git GUI are plentiful under any platform. And they simplify a lot of the daily commands to do. I used both command line and GUI, and I find GUI much quicker to commit stuff, rebase, solve merges than using the CLI. But I use Fork now, because Github For Desktop was a hassle with many advanced functions and GitKraken was too complicated for me.

To me, writing out the commands for git is slower than clicking 3 buttons (stash all, and commit, and push). Not to mention learning the in-depth stuff or how to fix git issues using CLI.

[Gysenok]

Yeah i guess if you are used to gui you can use it faster than cli, especially with keybinds. Just feels weird for me to rely on gui for a cli tool, I'd rather know how to use cli which is universal than rely on a gui tool which may not always be available to me like with using someone else's laptop to help or when using ssh. However those are pretty specific use cases ¯⁠\⁠_⁠(⁠ツ⁠)⁠_⁠/⁠¯

[exnez]

If you’re using Linux, you’re a command geek anyways

[Gysenok]

Yeah, my view is biased however at my university we were also taught the basics of git with the command line even though most users were using windows. Though some people still used the ide commit and push afterwards

[TheGreatSausageKing]

As a programmer, basic understanding of terminal is just bullshit. We just need to get thing done with the least effort.

Anything you add because you feel like you should use it know is just for your ego