How I'm still not using GUIs in 2019: A guide to the terminal
1–10 of 248 posts
Re: How I'm still not using GUIs in 2019: A guide to the terminal
#2> To avoid the annoying seconds in which vIM would freeze during tasks like syntax-checks, neovim lets you run jobs asynchronously.
Vim 8 also has asynchronous tasks, as well as a builtin terminal emulator. So there is not much of a reason to use Neovim (except Lua scripts, maybe?).
Re: How I'm still not using GUIs in 2019: A guide to the terminal
#3> To avoid the annoying seconds in which vIM would freeze during tasks like syntax-checks, neovim lets you run jobs asynchronously. Vim 8 also has asynchronous tasks, as well as a builtin terminal emulator. So there is not much of a reason to use Neovim (except Lua scripts, maybe?).
Without neovim, there would probably still be no asynchronous tasks in vim.
Sometimes a little bit of competition is very well perceived.
Others will probably chime in with the technical merits of neovim but for me, this reason alone is good enough.
Re: How I'm still not using GUIs in 2019: A guide to the terminal
#4I 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?
Re: How I'm still not using GUIs in 2019: A guide to the terminal
#5> To avoid the annoying seconds in which vIM would freeze during tasks like syntax-checks, neovim lets you run jobs asynchronously. Vim 8 also has asynchronous tasks, as well as a builtin terminal emulator. So there is not much of a reason to use Neovim (except Lua scripts, maybe?).
"there is not much of a reason to use Neovim (except Lua scripts, maybe?)"
Vim has allowed scripting via Lua since before Neovim existed.
Re: How I'm still not using GUIs in 2019: A guide to the terminal
#6I 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?
So you edit with ed? :). Also anything wrapped inside tmux would definitely defecate if hooked up to printer.
Some jobs are interactive. TUIs ain't bad for those.
Re: How I'm still not using GUIs in 2019: A guide to the terminal
#7For me, things like VIM where you first have to configure the hell out of it are a pain. Every time you're on some other machine, all your customization is gone. So after switching machines a bazillion times over the years, making the same little tweaks over and over, I've learned to deal with the default config. What I didn't expect: It made me a lot more productive in the long run.
Re: How I'm still not using GUIs in 2019: A guide to the terminal
#8I 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?
[deleted]
Re: How I'm still not using GUIs in 2019: A guide to the terminal
#9I 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?
So you edit with ed? :). Also anything wrapped inside tmux would definitely defecate if hooked up to printer. Some jobs are interactive. TUIs ain't bad for those.
> Some jobs are interactive. TUIs ain't bad for those.
Exactly. A printer is an inappropriate output interface for an interactive job, it's not the input interface that's at fault.
Re: How I'm still not using GUIs in 2019: A guide to the terminal
#10I bloody wish there were a really good TUI toolkit for Python, something like Visual Basic for DOS but with a bigger selection of more advanced widgets.