Linux

48655 readers

1989 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

[email protected]

138

Why do you use the terminal? (self.linux)

submitted 1 year ago by Waffelson to c/[email protected]

162 comments fedilink hide all child comments

Hi, everybody Recently, a guy noticed that I was using it and asked why? For me it because in Linux many things are done through the terminal because Linux has many different desktop environments

He also compared terminal commands with cheat codes in GTA and other games, he understands what benefits you take from them, but not from terminal commands

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 18 points 1 year ago (2 children)

Because every IDE implementa a different git interface and I can't be bothered to figure out where they hid the commit, push, pull etc. buttons this time.

[–] [email protected] 5 points 1 year ago (1 children)

Damn I hate with a passion the IDE interactions with source control software. I may make use of the visual information they give me, but I still execute the commands in the console.

[–] c10l 3 points 1 year ago

Same. Git GUIs can be great for examining commit trees, visualising patches, etc. For any write operations (this includes things like fecth and pull which write to .git), it’s all in the shell.

[–] [email protected] 5 points 1 year ago

When teaching programming classes it's awful trying to figure out every IDE's git interface that my students are using. Each IDE puts the buttons in very different layouts and they even change the names of the buttons because they don't like the way git itself named operations. It's untenable to know them all and actually be efficient and helpful as the instructor.

Instead, I say they're welcome to use the IDE, but the class materials use the canonical underlying command line tools and terminology. They just need to search for how to translate the real git interface to however their chosen tool does the same operation, but it's up to them to figure it out.

When they do ask for help, I bring up the terminal (usually even inside the IDE) and run the git commands just like we went over in class.