Satisfying my own curiosity #1:
Who here uses Vim/Neovim, and who doesn't?

I'd appreciate straining from discussions, ideally 1 comment per person starting with the name of your IDE (it'd make counting easier).

Im using VS Code (VS Codium actually), though I am looking for alternatives but vim nor neovim never clicked with me

I use vscode for regular development and notes (mostly markdown). I never use the terminal in vscode so whenever I find myself needing to check a quick file, I'll use neovim because it has pretty colors

why would anyone use Vim - in a world where nano exists? The One True cli-texteditor.

as for the IDE of my choice: the whole jetbrains-suite, depending on what project i'm working on.

I use the whole Jetbrains suite.
That and Nano.

Basically tosensei's answer.

Visual Studio Pro

#corporate #30-years-a-noob

@tosensei nano can't delete 30 lines of config with 4 button presses

VS Code daily driver
VS at work, daily driver 2
Neovim occasionally. Just ended a two day stint of practicing, back to VS Code to get some heavy work done, then I will likely return to Neovim when all caught up

@lungdart the amount of time i ever needed to do that in a command line, in my life, is exactly zero.

@tosensei that's one of those things you don't know you need to do until you start doing it.

Bulk operations on blocks of text are extremely powerful.

Mass select, mass copy, mass paste, mass delete.

Not to mention the underlying motions that enable these operations are useful on their own: jump to the start of the line, end of a line, start of the word, end of the word, start of the paragraph, end of the paragraph, start of a block, end of a block, start of a file, end of a file, jump to line number, jump ahead 30 words, etc etc.

Once you learn this workflow, nano will feel like youre an Olympic runner stuck in a wheel chair.

@tosensei another way to think of it.

A carpenter without an oscillating multi tool: "I've never needed one of those in my career, ever."

A carpenter with an oscillating multi tool: "This thing has so many uses, it makes me more productive"

@lungdart the thing is:

whenever i need to do those things, i'm not doing it in a CLI. even when i have to work over ssh, i simply mount the file and open it in a proper editor.

having all of those features crammed into a CLI-editor is like putting an osci-multi-tool, a power planer, a cnc-router and a chainsaw onto a bicycle.

@tosensei ones a text editor in a gui. Ones a text editor in a cli.

They are both text editor features on text editors. Cli has nothing to do with it, other than preference.

And vi has been doing this a lot longer than any gui text editor.

You know what? You're right. I waive the "no discussions" clause of my original post. Discuss away! I regretted it as soon as comments started flowing in, and I wanted to ask questions myself.