Live data from Hacker News

How I'm still not using GUIs in 2019: A guide to the terminal

lucasfcosta.com

81–90 of 248 posts

Re: How I'm still not using GUIs in 2019: A guide to the terminal

#81
post #61

What's with capitalizing it vIM? Website, man page, :help, none of those have it capitalized that way.

Weird, right? You'd think it was a typo, but it was a very consistent typo. Maybe they did it lowercase, then they `s/vim/vIM/`, hitting CapsLock and Shift at the same time when they wrote that.

Re: How I'm still not using GUIs in 2019: A guide to the terminal

#82
post #18

I'm a game developer mainly writing/reading/debugging C++ on a codebase that's well over a million lines of code. As with most game-dev I'm developing almost entirely using Visual Studio, and I can't imagine trying to navigate code using a terminal based editor. Maybe it's just because this is what I'm used to, however I just don't see how some of the tools would even be displayed in a terminal (parallel stacks windo…

Some game devs prefer to use VS with an external editor (as shown by Casey Muratori and Jonathan Blow in their live streams).

Re: How I'm still not using GUIs in 2019: A guide to the terminal

#83

The world moved from CLIs to GUIs. Guis have not only persisted, they've improved. If someone insists on using a CLI and nothing else, after all these years of the world having moved to GUIs, I wonder what prejudice is behind it. How, reasonably, can all these tools beat a thing like Visual Studio? Must limit job opportinities too...?

> Guis have not only persisted, they've improved.

Respectfully disagree. They've bloated up over time, and lost information density due to trends emphasizing lots of whitespace and hiding options. I liked my GUIs from 10 years ago better, thank you.

> If someone insists on using a CLI and nothing else, after all these years of the world having moved to GUIs, I wonder what prejudice is behind it.

It's not prejudice, it's pragmatism. CLI and vim/Emacs tend to have much higher productivity ceilings (i.e. there is something to master, and that mastery brings rewards). They compose better too, so you can solve more problems without starting to desperately bend the problem into the shape of your tool. They're also lighter, faster, enable easy automation (which is the whole point of this job), and can be used remotely.

> How, reasonably, can all these tools beat a thing like Visual Studio?

Because IDEs can be seen as one particular arrangement of those tools. It tends to cover the most common use cases, but you cannot really step outside it. Whereas "all these tools" used directly can be arranged in different ways, solving more problems.

> Must limit job opportinities too...?

No, it doesn't. With IDEs there's little to no expectation of "proficiency" there - after all, the GUI is there so that you don't have to know your tool.

Re: How I'm still not using GUIs in 2019: A guide to the terminal

#84
post #4

I like command-lines. I don't like TUIs. Here's the litmus test for whether a program truly belongs there: Would it shit the bed if its stdout was a printer?

The Amiga was like that. It didn't physically have a text mode, so there was no point to TUIs. The console (a GUI app that displayed text) was primarily command based. Anything screen oriented (even the first version of Vim) was a GUI app.

I kinda wish we'd move beyond the GUI/text dichotomy. I wish we had something more like the Listener on Symbolics Lisp Machines, which could show rich text and images, forms, clickable elements etc from within a console environment.

Re: How I'm still not using GUIs in 2019: A guide to the terminal

#85

"Not every machine has VSCode, Sublime or Atom installed, but every machine has a terminal." I love that the article goes from this sentence immediately to: "These are the main programs I use to make my terminal a complete development environment:" And proceeds to list 5 different programs, some of which are only available on macOS. Brilliant. Edit: One of which are only available*. My point isn't that there isn't a…

What?

iterm2 is the only OSX program in that list of five.

[edit] Plus, his whole point is that you don't need a GUI to get work done. Not, that you don't need software at all.

Re: How I'm still not using GUIs in 2019: A guide to the terminal

#86

"Not every machine has VSCode, Sublime or Atom installed, but every machine has a terminal." I love that the article goes from this sentence immediately to: "These are the main programs I use to make my terminal a complete development environment:" And proceeds to list 5 different programs, some of which are only available on macOS. Brilliant. Edit: One of which are only available*. My point isn't that there isn't a…

"Some of which" is actually just one app from the list (iterm2). Iterm2 is just a terminal emulator, so I guess you can sed "s/iterm2/gnome-terminal/g". I must admit that none of these are common default apps.

Re: How I'm still not using GUIs in 2019: A guide to the terminal

#87

"Not every machine has VSCode, Sublime or Atom installed, but every machine has a terminal." I love that the article goes from this sentence immediately to: "These are the main programs I use to make my terminal a complete development environment:" And proceeds to list 5 different programs, some of which are only available on macOS. Brilliant. Edit: One of which are only available*. My point isn't that there isn't a…

Using the terminal at least makes you proficient with the lowest common denominator of tools.

I know I can SSH into any random machine, and edit a config with the copy of vi/vim it has, even if it doesn't have my fancy plugins.

And if I get a new machine, all I have to do is install my tools via Apt/Brew/etc, clone my dotfiles repo, and run an install script.

Re: How I'm still not using GUIs in 2019: A guide to the terminal

#90

Earlier quoted context omitted.

Java in intellij+ideavim is much faster than in (n)vim, and that comes from someone who has been using vim for nearly a decade. Intellij is just too good.

Been using Vim for about the same length of time... And the times I have used those emulators they just haven't been the same. Does the emulator support VimScript? Macros? Plugins? async jobs like vim8? The terminal is my IDE I can open a file with a couple of keystrokes, run bash scripts from inside of my editor and just as easily be back navigating the terminal. Maybe I'm missing something, but I don't see how inte…

(Just in case I didn't make myself very clear: I'm talking about Java; any other language is another story, and for that I use tmux+vim) It's true that there are a lot of small things that slowly add up that make the experience less positive (especially if you have used it for a long time), and I often have vim opened in the background precisely because certain things are easier in vim (ideaVim does have macros, although I haven't used them enough to really say how good they are). Ultimately, I've realized that I miss Intellij more when I go from Intellij to vim than the opposite.
Post reply on HN