[azemetre]

When I first started to learn how to program I was following along a basic tutorial by Jeffrey Way and his first sentence was "We're going to use vim."

That tutorial, whose topic I can't even remember now, set me on a path for my professional career. During 2012-2015 there seemed to be way more competition in the editor space before VS Code gobbled the community mindshare. I remember starting my first professional job and having a coworker to keep pressuring me to use vim because he used emacs and wanted to argue with someone about emacs in the office (all in good fun I assure you :D). I think I started using nvim when 0.2 was release, but then I didn't really do much more with my rc file than what vim offered.

When neovim enabled plugin authoring with lua that's when it felt like the magic of neovim started to click for me. Plugins like telescope, harpoon, and fzf changed the way I fundamentally work now.

Although I think my favorite thing about neovim is watching other people use neovim, I'm always learning new workflows to introduce into my workflows. It sounds tiring, but it doesn't feel tiring if that makes sense?

Really excited to see inlay hints natively as that's something I really struggled to configure myself.

[celie56]

I love watching others use Neovim and that's how I learned more about the LSP / treesitter integration. I still find that VS Code is my recommendation for new contributors to an existing codebase because of how intuitive it is to resolve problems solo. If I want to debug a change in an existing project I will almost always reach for VS Code due to the integration with build systems (CMake for example) or other tools. That said, I find that I do "real work" in neovim: thinking, exploring, or writing this reply.

If I were to teach someone from the beginning I would still recommend (neo)vim.

[DEADMINCE]

> because he used emacs and wanted to argue with someone about emacs in the office

That's weird to me as in more than 20+ years I don't think I've ever been around people arguing that in real life. It's always been more of a meme to me than anything real.

[azemetre]

It was always good natured and I enjoyed the comradery that came from it. He also taught me a lot about vim and command line tools in general.

[sph]

> When I first started to learn how to program I was following along a basic tutorial by Jeffrey Way and his first sentence was "We're going to use vim." That tutorial, whose topic I can't even remember now, set me on a path for my professional career.

I like this origin story.

In my case, I was already a decent programmer and beginner UNIX admin when I got my first job, and one day I was using nano or some other "friendly" editor to edit some files on a server, when the literal grey-beard senior sysadmin that was looking over my shoulder pulled a face and said "OK, it's time you learn how to use vim", and spent some time teaching me the basics of it.

Now I have surpassed the Master and I use Emacs, though vim is still my second favorite editor.

[zabzonk]

back in the early 1990's i worked for a commercial training company (The Instruction Set) and the first day of our "Programming In C" course normally went something like this:

me: we are using these beat-up terminals

trainees: is this what we are paying for?

me: we will be using unix (no linux easily available then)

trainees: but we use VMS!

me: and we will be using vi to edit our programs

trainees: wha???

....a week passes

trainees: actually quite neat! i really like vi