News for hackers. Stuff that matters.
Re:A terminal-based workflow for research, writing, and prog... by __turbobrew__ on Thursday December 03, 2020 @08:26PM (#25297892)
Having a terminal-based workflow is a lifesaver in the era of work from home. When using a terminal based workflow I cannot tell the difference between working locally and working on a machine I have SSH'ed into located at my office (10ms round trip ping).

Even when I VPN into work, ssh into a box at work, then ssh to a jumpbox in AWS, and then ssh from the jumpbox to an EC2 server the experience is still flawless.

Re:A terminal-based workflow for research, writing, and prog... by bch on Thursday December 03, 2020 @10:22PM (#25298518)
I was thinking about this today - that is: a terminal (“minimal”) setup may well have prepared those of us who practice it - for remote work (great news if a pandemic strikes!)

I wondered though, if there’s no way to objectively “score” the advantage of, say, terminal-minimalism vs. GUI-maximalism, what might some discussions of t-min vs GUI-max be? What, if anything, does t-min really cut us out of while we’re preparing for the rare case of “Ok, imagine you’re stuck on a spacecraft with only a character terminal and a 300baud modem - what will you do then with your Windows RDP-available machine back on earth?” Am genuinely interested to hear people’s ideas of the calculus here.

Re:A terminal-based workflow for research, writing, and prog... by nbwl on Friday December 04, 2020 @02:12AM (#25299816)
Pros of t-min: - overall greater speed using a computer, you become what people call a "power user". - some sysadmin knowledge. Adopting a terminal based workflow requires to tinker with your system (systemd, sh scripts, building certain repo for a tool you want etc.).

Pros of GUI-max: - You don't have to spend hours learning and configuring things. - Certain tools are just better when they are built out in a GUI for you. I think here in particular of C/C++ debuggers, it's hard to get a nice experience in the terminal.

As for objectively "scoring" it's hard to assign real values. You could eventually measure speed. I have worked in production support solving a lot of benign problems on a day to day basis. This is when I adopted my terminal based workflow. It was way faster than my other teammates using desktop apps.

Re:A terminal-based workflow for research, writing, and prog... by bregma on Friday December 04, 2020 @07:59AM (#25301752)
> You don't have to spend hours learning and configuring things

After spending hours, sometimes days, trying to learn GUI stand-ins and trying to configure them (turns out you usually can't unless the GUI designer though it was a good idea), I usually give up and go back to being productive instead by using the CLI.

Re:A terminal-based workflow for research, writing, and prog... by desmap on Friday December 04, 2020 @04:56AM (#25300684)
> You don't have to spend hours learning and configuring things

I got 70% of my sysadmin skills because of hanging out 24/7 in the shell and configuring things.

Re:A terminal-based workflow for research, writing, and prog... by bergie on Sunday December 06, 2020 @10:12AM (#25323933)
It also makes development using a mobile phone possible. The Termux environment on my Android phone is identical to what I have on my work laptop.
Re:A terminal-based workflow for research, writing, and prog... by pjmlp on Friday December 04, 2020 @01:47AM (#25299710)
I guess you never did telnet over modem connections.

My RDP connection over VPN works without issues.

When it fails, using ssh wouldn't be much better anyway.