I know it’s silly, but Vim is single-handedly responsible for people thinking I “code fast” in interviews. I always chuckle when someone notes how fast I can manipulate code and I think about the learning-wall I hit when first picking up Vim.
I've only used vim for three years and it's been a fantastic experience. Every time I'm in a normal editor I long for vim. I think the most important video I watched about vim was about text completion in a thoughtbot meetup [0]. There I learned about ctags, the jumplist and ways to complete words, sentences, lines and blocks of code.<p>[0]: <a href="https://www.youtube.com/watch?v=3TX3kV3TICU" rel="nofollow">https://www.youtube.com/watch?v=3TX3kV3TICU</a>
OK, today is the day I donate to the children in Uganda. If I'd donated a penny every time I'd seen the vim splash screen, I'd have probably donated tens of thousands of dollars by now.<p>Thank you Bram.
Doing less work on Xcode and working more on servers made me appreciate vim alot!<p>I don't use any plugins (tried it back then with neovim and found the editor itself slow to load) and make me memorize folder structure a whole lot more since I'm using tmux alongside it.<p>I love the fact that I can hop on any system that has vim and I'm ready to go.<p>Happy birthday, vim!!!
I’m grateful to Vim because it taught me that I can write plain text. Previously, I was under the assumption that I need to create a Word or Google Doc. I wonder how many others are in the same situation I was in…
There’s a really fun online emulator that lets you use the original vim <a href="https://bit.ly/3k7vKDi" rel="nofollow">https://bit.ly/3k7vKDi</a>
Vim is what got me into using terminal emulators, the shell, and linux. I started trying to use it because a mentor of mine said "it makes coding fun again." It's the reason I moved from Windows to WSL, and from WSL to Linux. It's the reason why I started learning about core utils. When using vim, it feels natural (and even inevitable) to use the shell and cli tools.
Happy Birthday Vim!
This page helped me learn all the important Vim keys. <a href="https://vim-adventures.com/" rel="nofollow">https://vim-adventures.com/</a><p>Been meaning to try out Neovim after watching this episode of Dev Tool Time: <a href="https://srcgr.ph/the-primeagen" rel="nofollow">https://srcgr.ph/the-primeagen</a>
Happy birthday, Vim! Thanks to everyone who has worked on that project.<p>I've used vim for a while now, although not a power user I'm certainly capable. One of my favorite experiences with vim was remote pairing about a decade ago with another developer. He lived a couple of states over, and we paired by sshing into the other person's machine and using vim on a byobu session. It was also fun because both of us had different habits using vim and got to learn some stuff from each other.
I've never used Vim, but I use Evil mode and vim bindings everywhere. I'd have a much poorer relationship with my computer without vim modes.
It's pretty amazing that vim has remained relevant for that long, outliving so many other editors. On top of that, it continues to evolve. Even in the ~5 years that I've used it, huge progress has been made. The fact that coc.nvim works so well, even in vanilla vim, is crazy.
One of the best things about PyCharm and friends is the vim bindings. They are much closer to actual vim than other IDE plugins. This is the main reason reason I made the switch to using an IDE for Python development.
Happy birthday, Vim.<p>I'll just leave this here:<p><a href="https://mobile.twitter.com/vasudevram/status/1248583566897762304" rel="nofollow">https://mobile.twitter.com/vasudevram/status/124858356689776...</a><p>It's a plug for my vi quickstart tutorial that I first wrote for two Windows sysadmin friends of mine. They had been asked to additionally manage a few Unix boxes, and had asked me to make a small tutorial that could help them quickly learn enough vi to get by on Unix.
After using it, they told me it was helpful for that purpose.
Still rocking vim since 1997 and love it. But old age's getting to me and I'm now finding myself reaching for either Visual Studio or JetBrains CLion for my coding more and more these days.
I first started using vi in late 80's at the university on a shared multics mainframe. Then I stopped using vi after graduating, only to pick Vim in 2012. How times have changed, running vi from a dumb vt100 terminal to now running vim on a pc with nearly infinite processing power, with gobs of cores, memory, and storage that was considered unimaginable in the 80's.<p>Vi and vim has stood the test of time (along with C, emacs, Linux, etc)
Vim is a wonderful editor, but let’s not forget that ed is the standard editor[1].<p>[1] <a href="https://www.gnu.org/fun/jokes/ed-msg.html" rel="nofollow">https://www.gnu.org/fun/jokes/ed-msg.html</a>
I'm glad that this post led to the group of you all that took the opportunity to donate! Didn't think it would get that much traction, so it's especially nice to see some good come from it.
Been working with vim for 2 or 3 years. Now, when I don’t have it on any kind of text entry fields I get a bit disappointed. Happy birthday you revolutionary odyssey.