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
I’m a shell user too, but as programming languages I would rate Bash utter garbage. Fine for little piping but for longer scripts I will be reaching for Haskell.
Because I can do things in 30 seconds what two windows admins take 15 minutes to do with their point and clicking. Not even making this up, this happened.
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.
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.
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.
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.
I live and die by ssh and scp. Sometimes rsync for larger moves.
Once you’ve got ssh for terminals (used to be x sessions too!), then port forwarding and socks proxies, add in scp for file moves, and layer in sshfs for whole file system mounts it’s a potential combo for remote work and network tunnels. Such a phenomenal toolkit.
SSHFS is shipped by all major Linux distributions and has been in production use across a wide range of systems for many years. However, at present SSHFS does not have any active, regular contributors, and there are a number of known issues (see the bugtracker).
The current maintainer continues to apply pull requests and makes regular releases, but unfortunately has no capacity to do any development beyond addressing high-impact issues.
When reporting bugs, please understand that unless you are including a pull request or are reporting a critical issue, you will probably not get a response.
For tasks that I know, I’m faster in the terminal. For tasks where I’m less familiar or that are very important (like disk partitioning) I prefer a GUI because with a GUI I can usually see a bit better what I’m doing.
Terminal tasks for me include copying stuff, setting folder permissions, uncompressing or compressing folders, quick edits in vim, etc.
One could ask in return “why do you use a mouse”. The answer is probably “I’ve always done it this way” and not “after trying out different methods it’s the one that i prefer”.
Add comment