What percentage of your computing do you do inside of a terminal vs inside of a gui, Jow Forums?

Maybe 5% Terminal. Most of it's GUI based but there are some tools that are just better to use terminal for when things get weird. Like git and docker.

I wouldn't bother to consciously go "more terminal oriented" unless you're some Linux Server admin, but knowing the basics is useful.

Idk, I only use command line to install/update software and edit config files, the rest I do in GUI applications.

Foreplay comes first, user.

Quite sure it's 50/50 but depends on the day i guess. Sometimes i'm more of a programmer and others i'm more a engineer.

There is a time and a place for m'lady

>thotposting

Attached: 1567722994093.jpg (351x313, 74K)

nah, for programming a text interface/CLI is better. CLI applications are much smaller and more composable, and since everything is text its not hard to manipulate output however you want to display it or feed it to another tool. You can't do that with a GUI, you are stuck with what GUI application supports. Programming is text and most programming tools are made to be used from the CLI too, so the environment there for programming is great. You just have to put a little bit of effort into learning it. I always am in Emacs these days and never leave it except to browse the web.

that sounds very boring compared to tasting the most delicious part of a woman/boy

The only things I still do in terminal is version control and build tools (ala maven and gradle). For some reason they have a higher chance of freaking out when done using GUI in my experience, or just not working the way in would expect

30% in terminal (moving files, running servers, processing text, vi, irc), 70% in a browser (vscode, messaging, email).

The rest of the GUI is just a convenience for tiling my browsers and terminals.

/thread

Me too

1% for just booting/installing React, commit github, Yarn/npm.
And for Maven repo i just need t copy paste

>70% in a browser (vscode, messaging, email)
Based

>Is it worth the learning curve to go more in on terminal programs?
99% of CLI uses one of 3 ways to interface(arguments, stdio, ncurses-like). None of these is as intuitive as gui by itself, but once you get comfortable with them you can just use any terminal program with ease. GUIs might be easier to learn, but every GUI is different and each require non trivial amount of time to get accustomed to. They also are much slower and impossible to combine. When you use terminal, you can pipe processes together, write scripts and automatize your task to greatly improve efficiency.

discord trannies flooding Jow Forums with yellow fever again

s

AAAAAAH IM COOOOOOOMING

Whats their end game?

Attached: 1532129809026.jpg (600x887, 91K)

yes command line programs are very flexible and powerful if you even half-kinda grok them
I mean the web runs on "hypertext", what is the terminal but, ah, perhaps a level lower than hyper..."supertext"?

Forgot to mention, its easy to write your own text based tools for your workflow and plug them into your workflow somewhere thanks to small and composable CLI applications. GUI doesn't allow that.

>their
why are you referring yourself as a group?

Attached: before surgery.png (1291x972, 3.22M)

it's ok, Jow Forums is here for you

Attached: 1350682011763.jpg (750x1000, 193K)

This makes me want to try and see if I can manage to use my pc without a mouse

bhutanan-chan why did you stop Shir posting?

tfw you will never feel another persons warm skin and body

Actual programming in an IDE cos I'm not a Luddite. We use scripts to automate builds and tests in Jenkins. Manual builds and runs are usually CLI cos our software runs on specialist equipment that runs console only Linux.

I don't do much in a terminal at home, mostly GUI. Significantly more terminal work when on the job, especially since I need to log in to various headless VMs, but a lot of GUI work too. Terminal is only really useful to me if I need a semi-automated way to do something a GUI does not provide or as I've said to log on to remote, headless machines. I'm not going to open a terminal to move a folder to a different location or shit like that.

>tfw you will never wear another persons warm skin and body

1%

feels good man
fuck human contact

and so horny.

Being lonely is alright, learn to build up yourself. Feeling alone in the world is not good, if so I suggest some friends or socialize.

100% terminal, yes I am that hardcore.

Attached: 1568618949288.png (547x312, 126K)

It's weird because I feel more at ease working inside a GUI environment and yet, most of the windows I open are terminal emulators.
Let's say 50/50.

Attached: Nom nom nom.gif (320x180, 481K)

GUI's are much more cumbersome than using the terminal, even for basic shit like opening files and making directories etc.

The terminal is not intuitive though, I really hope we'll get GUI ONLY operating systems someday.

Attached: 1548706987984.png (1152x900, 16K)

The only guis I really use are chrome, steam, and nm-gui.

Why are you using proprietary software faggot?

Because I like g-sync.

>The terminal is not intuitive though
So? Making an inefficient but intuitive system isn't very smart when you can make an efficient system that needs minimal prepping.

No women (male)

Cope harder

About 90% terminal because I don't have a cute bubble butt Asian girlfriend. I would just use windows if I grew normally and weren't a 24 year old virgin.

Depends on where I am and what I need to get done.
At home there is barely any call to fuck around with a terminal unless I am working on some personal project like setting up servers or whatever.
At work I prefer being in a terminal 90% of the time. A lot of the work I have to do requires me to find things, edit things, and basically work pretty much with text and files with text. Start servers, stop servers, etc etc.
This is all immensely easier in a terminal, specifically Unix or GNU/Linux terminal because of the tool sets that present themselves.

Just take this basic problem.
If I have a directory with a thousand files in it but I need to know which files have a certain string do I want to waste my time opening each file in a graphical editor and using that editor's search function? No. I can simply grep -l "string I'm looking for" * and get what I need in fractions of a second.
Indeed, working through a terminal gives me all sorts of options to do work efficiently and far more clever than any GUI can really do.

A side note about GUI based tools is that often times when trying to give the user more options and freedom in the tool it becomes a monster of too many options and functions. Also "wizards" and other such things to help hand-hold the user through the tool's process which just makes things more and more frustrating. Windows and in particular microsoft created tools are the worst candidates of this as often times I just want to do a single thing and now I got to answer to all sorts of pop up boxes.

The actual learning curve of the terminal is not so high. It is just the thought of the textual interface compared to a visual one that is so difficult to get.

The terminal is actually very easy. Basic steps:
1. What do you want to do? Get a table of commands or google a program that does what you want.
2. use "man $prog" or "$prog --help" and read
3. learn what STDIN, STDOUT do and how to use basic pipes aka ">" "

almost 100% terminal. i use firefox for posting on Jow Forums and email because elinks javascript support isn't up to task and email providers spaz out for some reason when you use the imap service they provide. for some reason my email kept getting locked up for "suspicious activity" and i would have to use firefox to unlock it, so i just gave up and started using their web client.

terminal is easier because i use the tty with tmux so everything is a hotkey. after you become comfortable with bash scripting things like renaming and organizing files takes 1/10 the time as using a gui. my chromebook has a buggy tty because the gpu driver is junk so i use spectrwm and xterm on it.

suicide

I don't understand any of what you just said.

ARGGHHH AAAAAAAA IM GONNA COOM AAAAAAAA IM COOMING AAAA FUCCKKKKK AAAA COOM COOM COOM PSHSHSHSHSHFLPFLPFLPFLPFPLP AAUUUUGGHHHHHAHAHHAHHAAAAAAHHHHH NNGGGGGGGGGGG OOHHHH YEEESSSSSS COOM COOM COOM PFLPFLFPSHSHSHSLPSLSH

Terminal programs can usually be scripted or automated a lot more effectively than graphical stuff. The end goal is not interactive tools but daemons that do your work for you. GUIs are good for inherently graphical tasks like displaying or editing images/video, but sub optimal for everything else.

5% terminal. it's shit.

70/30 terminal/gui

My GUI is inside a terminal so 100%.

Attached: 1563063907202.png (306x36, 2K)

90-95% GUI. Web browsing, image editing, music, text editing, all graphical.
The CLI gets used for quick calculations, compiling shit, small scripts, and batch jobs (eg, converting shit with ffmpeg or imagemagick).

brap

Yeah you would have to be literally retarded to use an inferior product, where half of the options are stripped away and hidden behind menus, and the program is locked behind a startup time, and won't accept input innately from other programs.....

Attached: 1555700138464.jpg (808x446, 139K)

That's why GUIs are for most people, but when you are professional and serious you learn tools that accelerate your workflow in future, really not that hard of a concept.

AHA HAHHHH UHHHHHH ITS COOMING I CAN FEEL IT NOW AAHHHGH

IM COOMING FUCKKKK

Attached: 1568628271874.png (629x275, 85K)

I would use the terminal more if I could memorize every single command I ever use(without looking through history) and what every argument does

I want to violently crash my face into that soft pink ass and give the biggest, lung-exploding whiff of the century

That just means you're uninformed and/or retarded.

spotted the virgin

When I'm working my pajeet job I use either intellij or vs depending on the project language. However, I do a pretty good bit of C programming in my free time. Since I write it for Linux first but the host OS is windows I do everything through WSL. I've gotten more than comfortable with using vim+tmux on the fly with cmder so I'd say it was worth it. The only C IDE I tried to tackle my personal projects with was CLion and it was a mess that wasn't worth the amount of memory it was using. Considering the lack of autocomplete anyway and the suboptimal syntax highlighting compared to intellij, vim offers basically the same thing without the JVM hogging my memory.
tl;dr I use vim in wsl because it lets me stay close to the Linux environment and I wasn't happy with CLion.

I do somewhere between seventy to eighty percent of all my work in a terminal because it's fast, simple, and intuitive. The only times I use a GUI are for web browsing, image manipulation, and editing audio.

Yeah, I just remembered I'm retarded.

faggot

Most days, the only gui i use is chrome aside from shit like slack and finder

you saved a brother today user, god bless you.

The learning curve is low, like others have said. It might feel tedious, because it's not something you've used most of your life.

why is jap ass so perfect?

Maybe a 1/3 of stuff I do in cli

Attached: 1564780276630.jpg (645x773, 41K)

you like fictional things?

90% in the terminal, then again Im actually employed unlike most of Jow Forums.

I'm employed, just not in the job I want.

Brainlet detected. Terminal use is a language, not a list of commands to memorize by rote.

>robot waifus

soon my brothers, soon

41 percent yourself you sick fuck

fuck off Jow Forums

dial 8 sicko

99% of my time at work is spent in a terminal, and at home, the only non-terminal application I run at any given time is a browser.

I smell larp

>Not browsing in w3m

vocaroo.com/i/s1k5N2N3GV4o

pic related user. im in the same boat.

Attached: the_fox_and_the_grapes_by_dreoilin_d5tvcf6-fullview.jpg (602x748, 147K)