Only @ThePrimeagen can make it look so easy.

@ChrisGVE

Жыл бұрын

Very true, he's a master. I've switched to neovim about 2 years ago and it was a process to get used to it but now I couldn't go back. So much so that when building a custom keyboard I install a custom firmware that is inspired by neovim: my arrow keys are hjkl system wide and I also use YXP instead of the usual copy/cut/paste. But I can also understand that investing for switching to a different editor is not in everybody taste.

@jaroslavhuss7813

Жыл бұрын

When I saw the headline with Vim, I was so sure you have watched ThePrimeagen's videos... Did you noticed, that Vim is BLAZINGLY FAST? No? Neither do I :-)

@semikolondev

Жыл бұрын

Neovim is better to start.

@ChrisGVE

Жыл бұрын

@@semikolondev Yeah more sensible defaults than vim

@AlexNiebla

Жыл бұрын

You should have installed NeoVIM

Very fun video. I'm a Vim user for 10+ years and have tried switching to VSCode, but with the exact same arguments I gave up, and returned to Vim to get my job done. 🙂

@AZisk

Жыл бұрын

So THAT'S how the other side lives :)

@casperes0912

Жыл бұрын

VSCode has a Vim mode where it pretty much acts like a Vim editor

@briansrensen6603

Жыл бұрын

@@casperes0912True, and other editors like Atom also has Vim mode or Vim bindings. But there is always something that's not exactly as I'm used to and If I just turn the other editors into Vim then I don't know why I'm switching anymore. There are also a ton of extensions to Vim to give it functionalities like VSCode, Sublime or Atom. I have more or less just accepted that it's not really worth the effort (or I'm too old to learn a new editor). 🙂

@briansrensen6603

Жыл бұрын

@@AZisk For me Emacs is the other side. That feels so alien to me.

@emanuelturis4132

Жыл бұрын

@@casperes0912 it's never really the same thing, you can't modify VSCode to the core, so it's impossible to replicate the same workflow from vim. I also tried multiple times to go back in the past, but am now happy and muuuch more productive with vim.

Vim in 100 seconds was right over there

vim user here for 25+ years. I really feel for you, man. Why on earth do you want to subject yourself to this steep learning curve? It would be months before you get to the same productivity level as you are now. AND, BEWARE! If you do persist and vim commands become engrained into your muscle memory, there is no turning back! You won't be able to use another editor unless it provides vi-like key bindings. I know I do. I have installed Ideavim in Intellij/Android Studio and enabled Vim Mode in Xcode, otherwise they are completely unusable to me. And of course when other people see me editing files using just the letter keys, they think I perform magic. But as I said, 25+ years. My advice to them, and to you, is simply "don't". Or do, but you have been warned...

@richtraube2241

Жыл бұрын

Muah hah hah!

@karthikreddy1301

Жыл бұрын

+1 for Ideavim plugin

LOL -

As a person that uses vim pretty much exclusively for development, I’ll say it is definitely an extremely steep learning curve, 5 years of vim and I’m still learning new features. That being said, once you’ve mastered it, there really is nothing that competes. When you add tmux into the equation, you can’t be stopped. To answer your question about why not use arrow keys, it’s because you have to move your hand, loss of efficiency, definitely took me a couple years to get used to. I think what a lot of people don’t realize though is the super powerful search/replace and copy/paste capabilities between files. There are also tons of plugins that add a lot of features, and most importantly it is super helpful for headless development. It’s powerful and fast whether you are on a MacBook, a raspberry pi, or even another system on a super slow connection. That being said, if you are developing front end stuff, it’s probably not super useful. If you are developing C#, visual studio is definitely the best option since the intelligence can nearly write the code for you. However, if you are doing embedded development and you know how to use a keyboard, then vim is definitely something worth taking the time to learn.

@AZisk

Жыл бұрын

Thanks for breaking it down like that by dev roles - would have been a great addition to the video.

@TJ-hs1qm

Жыл бұрын

the og vi can be traced back to ED a single line editor. the hjkl keys are part of that history and the hardware that was available back then. nowadays with relative line numbers and the f key I rarely use arrow keys.

@TJ-hs1qm

Жыл бұрын

on the computerphile channel there is a great episode on how the grep command came about and the limitations they were facing.

@skaruts

Жыл бұрын

*_"That being said, once you’ve mastered it, there really is nothing that competes."_* I'm very skeptical of that. I've watched quite a few videos of Vim, trying to figure out what is it that Vim does so much better than other editors, but so far all I could find was people overselling features that also exist in Sublime, or things that Sublime can do just as easily, or in many cases even easier. Probably VSCode can do all of it as easily as well. A lot of things people say about Vim are myths, too. The notions that using the arrows or the mouse affects productivity are myths. The majority of work time is not spent typing text, but thinking, reading, etc, so at the end of the day whatever microscopic advantage you may get for not using arrows or mouse, or from using feature X or Y, that won't matter at all. That is if there's any advantage at all. In other editors you also gain time for using shortcut keys instead of typing colon->command. Clicking something might also be faster in many cases. And it doesn't take months or years of getting used to. (I do a lot of typos, so, personally, using commands is a nightmare to begin with.) *_"That being said, if you are developing front end stuff, it’s probably not super useful."_* Indeed that's what I've started suspecting, that Vim is only useful in specific situations for certain people. But most people who talk about it don't seem to realize that.

@oleksandrsimonov9200

Жыл бұрын

The thing which is not exist in any editor and it’s really was the main reason I have installed vim mode in VSCode is a visual blocks editing.

Interestingly I recently switched from VSCode to VIM/NeoVIM. It takes time and patience to get productive in VIM but once you master it.... man, you can flyyy! Sorry it didn't work for you. Cheers!

Great video! I love that you gave it a chance and thought you were extremely fair. I enjoy using Neovim when I can. I am not realistically able to use it for work due to the projects I worn on, so I have the vim extensions installed in both Visual Studio and VS Code. This works pretty well for me since I am still able to use most of the things I like about vim even if they are a bit sluggish.

Thanks, Alex. I have to admit I enjoyed watching you suffer. And I admire your stubborn determination. After 40 years of using vi and its descendants, I sometimes forget how baffling it all is to newcomers. For better or worse, hjkl and all the other keystrokes long ago became permanently burnt into my muscle memory. I'm exactly the opposite of you: I get confused by arrow keys. For someone who is a blazingly fast touch typist, learning vim will probably increase their productivity. But, honestly, for most people, it won't be worth the effort. If you're comfortable with vscode, I highly recommend you continue using it. For me, when I first discovered vi in about 1981 or so, it was a huge step up from the line-oriented editors I had previously been using. But there were no such things as GUIs or mice at that time (unless you worked at Xerox PARC). I'm sure if something like vscode had been available, I never would have bothered to learn vi. You have a finite amount of time in your life; invest it carefully.

@dr.mikeybee

Жыл бұрын

I remember the terror of discovering that there was only the ed line editor on certain machines.

@richtraube2241

Жыл бұрын

@@dr.mikeybee I can't say I've been there because I always had vi or emacs available on the Unix machines where I worked in the 90s. But, yeah, I can imagine the horror. I like Ed for small fast jobs and would be very frustrated having to use it only.

Love that you run the exiting Vim joke right away Alex xD

I love vim. But I sadly often need to switch between editors based on my project requirements. What I've found interesting is that on specific keyboards where I've used vim the most I naturally fall into those vimbindings without thinking about it and it is frustrating when things don't support them. The other thing is I've gotten a bit of RSI from using my mouse so I try to keep my hands on the home row as much as possible

I've been there before, tried multiple times to learn Vim before but couldn't stick with it, until recently. I got tired of having to move my hands all the time to reach the arrow keys on my keyboard and decided that it was time to finally give it a real try. It was weird at first but by allowing myself to slowly learn bit by bit and making adjustments as I go, I finally managed to be able to use it daily, with the plugin for VSCode. Which like you said, gives you the best of both worlds, the GUI from VSCode and the movement from Vim.

I first tried vim in February. I hated it and went back to vscode. But then 3 months ago i realised that i had created so many shortcuts for my vscode, and i wondered if there ways a better way. So at the beginning of this month, i started using vim (neovim) It was a very steep learning curve and a lot of things to configure. But i now can't work without it. I can go for 3 to 4 hours without touching my mouse once.

It was very interesting seeing someone's perspective as a beginner to learn Vim. I think that given maybe a month or two, anyone could code faster with the Vim motions

Recently started using VIM. Definitely took some pain but getting faster by the day. noticed whenever i had to use a IDE for work, i started accidently using VIM keybinds, so i feel like its improving.

@brandon9638

Жыл бұрын

It only gets better, especially when you start scripting vim.

@nihancj

10 ай бұрын

How far along have you come? Tick tick it's been 9 months

@DrSnakeGamez

10 ай бұрын

@@nihancj unfortunately... nowhere 😂 i need to somehow integrate things like this in my daily tasks, else i will eventually start forgetting to use it... i'm weak

Vim is awesome ... but the learning curve is quite nicely represented by this character: | You summed it up perfectly. If you can or if you're willing to invest the time, it's gonna be great. I think I know approx. 2% of what Vim can do but these 2% are the reason why I have it in arms reach. When I have to make a text-horse out of a text-donkey it's my tool of choice and I find it quite funny how my stupid brain manages to remember how to tell Vim what to do.

@elorrambasdo5233

Жыл бұрын

So often I find myself watching myself use Vim. More than a few times, I thought the wrong command but did the right one.

Great on your part to give it a try! I started using VIM 6 months ago and have never looked back. The issue here is that VIM in itself will never provide you the same experience like VS Code out of the box. You will have to create your own config using plugins like coc and tree-sitter for code completion and syntax highlighting (also for file browser). But I understand the sentiment of getting work done since the learning curve is so huge that you will need extra motivation + time to invest in it. If you don't have that now its ok, maybe sometime in the future you can try again. But its a great one time investment 👍

VIM is installed if you open the terminal... Vi was great 30 years ago back when everyone used Elm for email... there are much easier options today. But I LOVE this video :)

Been Vimming for 20+ years and it is very hard to use a non-modal editor, selecting lines seem to hurt

Use NVim or NeoVim is more cutomizable - you can customise your IDE of choice as code interpreter in it . Vim is also nice . The Primagen is a guru in VIM

Congrats for the 100k subscribers

Hello @AZisk I'm planning to get the m2 MacBook air with 8 core GPU, 24gb ram, and 1tb SSD, for a software development do you think that 24gb is overkill or ok? because a lot of people in KZread said 16 is enough but I don't want to ran out of ram I'd like to add that I will graduate after 3 months, that's why I need a MacBook powerful for the software engineer job that I will apply for, I like the air for size and the color I don't like the heavy MacBook pro so I don't care for the extra money to have great performance

In university labs we had to telnet into Linux sever and do everything in cli and vim. Only programming in c or cpp. The black screens laid my foundation and now I appreciate visual studio a lot more. But if someday doom comes and a terminal is all I have , I will survive 😂

I ‘ve started with vim for my ruby projects some 10+ years ago. I switched to Elixir and editor remained the same! All workflows I had with a little config changes remained. It’s not easy to start, but for backend development it is worth

I live in vs code + vim extension installed. It’s incredible, love it.

I learned a very little bit of VIM in an afternoon and although I mainly use VSCode I find I like Vim for when I want something lightweight and quick to work with from the command line for small things. That and the search and replace strings can be really useful from time to time.

I use it occasionally when I'm on a terminal over ssh, I only know the basics so I don't suffer, and I can get simple things done. For anything more complex than simple edits I use vscode over ssh. I've had a friend who could navigate in between files, split the viewport, and actually work efficiently with it, but I like vscode, mouse is not my enemy. I like vim and I respect it, you can easily record and playback macros and all, but I rarely use it.

I've been using only Vim for text editing since October 2019. I started by forcing myself to use it. I read a few blogs and seen a few videos to get started. To this day, I have to admit I still use the arrow keys for navigation. But, once I knew how to get into Insert Mode and out of it, it was like using NotePad. From then on, I started to learn the motions and the different keys used in Normal Mode. Someone even said that learning Vim is like learning a musical instrument. You get better every day. I don't have to move my right hand all the way to the mouse for editing text. After getting used to the Vim way of doing things, I immediately installed Vimium; a plugin for Chromium-like browsers that uses the keyboard and has Vim-like motions to move around the browser. Finally, I try to install a Vim plugin everywhere! I hope you give Vim another try!

Great video. IMO, simply learning the vim motions and modal style editing gives you a big advantage in coding efficiency. I couldn't do it any other way. Every once in a while I get in the mood to go full vim and its good for a while but I always find my way back to IntelliJ. The vim motions and modal editing are always there though.

I learned VIM 2 years ago, these were my initial reactions, but now I don't want to go back, but if you want to turn it into a full-blown IDE to get features like auto-complete and going to code definitions, you might spend time tuning your setup using plugins and scripts, VIM is like a house without furnitures and appliances, you choose your own stuff and that can take a lot of time

"What the hell did i just do?" is a very vim sentence.

Back in the day terminals did not have arrow keys. I use vim in VSCode. Saves you a lot of time copying lines, deleting and replacing words, and finding words. Also great to delete lines, undo -re du

"We have no time to sharpen the Axe - we have to cut treeees!!!"

ESC+:+q+Enter. This one rule can save lives.

Neovim user here. I wa so happy on VCode on 2020 I changed my old intel Mac for a M1 Mac mini. When the pandemic ended I found my self without a laptop, so I bought an iPad, since I wanted to get things done while on the move I set up a remote environment, now I connect to my home Mac from mi iPad using Tailscale. But if don’t get vscode on the terminal, my only alternative ended up been Nvim, so put the time on it, it was paint full at times, but now Neovim is my default code editor, I have everything I need, code competition, syntax hilglihting, intelligent code navigation. And I move really fast on my code, compared with vscode, probably because VS is so easy to use that I didn’t give the time to learn to move really fast.

Same for me, it's a matter of getting work done. I'm sure Vim could make me faster after months of learning, but it's hard to find time to invest that sort of time and slash my productivity a ton for a substantial amount of time. Then again, I felt the same about Typescript vs JS, and now I'd never pick JS over TS for a project again. But I suspect the learning curve there is still way less steep than for learning vim :D

@AZisk

Жыл бұрын

very true. TypeScript still sometimes feels like more work than it has to be, but in the end I’m way happier with the code I write than just pure Javascript.

WOW! You exited vim easily. You are the quickest vim learner in the world.

Am a vi or vim user and I agree that it had a steep learning curve. I mainly use it to edit config files on my application / web / db servers

I learned vi back in the 1980s on Unix systems because it was the editor that was pretty much guaranteed to be available. As far as I remember, its command syntax comes from / is compatible with sed which is kinda handy for batch processing text files or doing macro like stuff in the editor. I still use it occasionally but, when there are so many great editors out there, I can't see why anyone would really care about it outside of a terminal setting. Still, I have friends who swear by it and at least it's not Emacs 😁

I code since more than 30 years ... used a lot of weird editors ... but never got used to vim - I always hated it when I tried! Always thought: What's wrong with me?!? Thank you so much for this video! 😉 Honestly, I kind of use only two fingers to type - and still I'm typing faster then I'm able to think my code ... ... so if I have to move my hand a little to reach the cursor keys is really not my problem 😝

I have been working as a backend developer for about 4 years, and I use vim on my day to day work. it didn't happen right away, it happened gradually: from simple commands => combinations of commands => custom keybindings => custom vimrc settings => plugins => custom plugins it sure does have a steep learning curve, I remembered I had to reference a vim cheatsheet all the time and work progression that day is like 10% (had to switch back to vscode to get some things done) but after investing time learning, coding feels like a game and is just, fun. besides that, it had lots of pros too: 1. vim keybinding are used in a lot of cli tools: less, more, w3m, git (diff|show|log --oneline), bash vi mode, tmux, etc... 2. you will get better at the command line (filters, use code to write code, which is also fun and efficient) 3. no extra gui programs to install, better performance (no gui eating up your ram) 4. it's been around for like 30+ years (stable), don't have to worry about being "sunset" and forced to learn a new editor (you know, like "Atom", how do you know vscode won't be the next Atom?) 5. it's just cool so why not? learn vim😎

I used IntelliJ with the vim plugin for 2.5 years. Switched to neovim with plugins as main editor 4 months ago. Love it.

It really takes interest, some reading and configuring, using plugins and some practice to really understand how powerful vim or modal editing is. in a month or so, you'll realize using vim you can really get your work done faster and easier than any other editors.

Wanted to do it for years, thanks for doing it for me.

The reason to use Vim over VSCode is the keyboard shortcuts. After you have all the short cuts memorized it's faster.

I mainly use VS Code for my undergrad work, but I am taking a course right now, Introduction to Systems Programming in UNIX, which requires us to program over ssh onto the school's linux machines and I have to use vim. I dislike it compared to VS Code, but I force myself to use do all my programming for that class through vim.

Tried Vim 30+ years ago. Managed to get the Emacs config file edited so I could install Emacs on my Sun Solaris SPARCstation, then never touched Vim again. Loved Emacs. My fingers still remember a lot of Emacs key sequences, which also work in some other environments. Favorite environment: Xcode. One I use now: PyCharm (wonderful). But best ever was the Xerox Interlisp-D environment; the editor understood Lisp structure, and was also the interface for the debugger. Editor, debugger, interpreter, all in one (sadly it is long gone, as is my youth).

"I have to use the j k keys to move up and down??!?! why not just the arrow keys?!??!?" as a vim/nvim user this is hilarious, why not? that's the right answer. I think that something new vim users need to understand is vim's philosophy of never having to look down at the keyboard nor move your hands from it. When knowing the basics, you could theoretically keep your wrists super glued to the desk and everything would be more than possible with vim/nvim. Awesome video Alex!

I've been using the Idea Vim plugin in Webstorm for almost 2 weeks now. I did spend some time to learn the key bindings and I was super slow in the beginning, but I'm starting to see a good improvements in speed. Right now maybe I'm at 80% of my productivity before vim. I'll definitely keep using the vim motions in Webstorm, I can just tell that I'll be waay faster after some more time of practice. I'm not sure if I'll ever make the full switch to VIM editor, but using the vim motions in Webstorm or VS Code is a no-brainer.

Alex thanks for the great content, can you do a comparison between parallels, VMWare Fusion and VirtualBox on M1 Macs

@AZisk

Жыл бұрын

thanks. the reason i haven’t done it is because VMWare doesn’t have a product released yet (it’s in preview and doesn’t have a lot of functionality). and VirtualBox is just not supported on arm at all

I feel Vim users aren't aware of the invention of the mouse.

Thought: you have Apple Silicon machine with 64gb of ram. Why not using JetBrains IDEs though?

Nice video! I switched from VSCode to Vim because I thought I could do more and better with it, but it doesn't necessarily. The difference is how things are accomplished. In my experience Vim/Neovim accomplish them in a more productive way. The biggest win for using Vim was the knowledge I gained, it makes you know your tool and customize it to extract its full potential. There is where I think many VSCode users fail. I've seen them struggle many times with simple issues with the Git integration, linting, formatting tools... because it comes almost as a built in feature hence an unexplored world for them. Vim made me deeply understand how linting, formatting, diagnostics, LSPs work, etc... to the point that today I could develop a plugin for Vim and even VSCode. Vim learning curve is big not only for the muscle memory you have to build but also for the custom configs you have to add and change along the way but it is a high pay high reward situation at least for my experience. I think VSCode and JetBrains software are great tools depending on the things you are trying to accomplish I just prefer using Neovim, in the end you should go with the tool that makes you feel safe and productive.

I use the vim plugin with vscode. I love it

Just started to use vim because I have a 2015 laptop and VScode is very chunky. I think people like vim for editing and rearranging their code or notes. In CTF challenges, when hacking a box, it may only have vim. So its also good to know.

I use vim in vscode and it is the best of both worlds. Outside of vscode I have neovim which is a little easier to use. One thing that helped me learn was to just leave vim in insert mode and implement the motions bit by bit. Great video!

A key point: Vim is not a binary "you either fail or enjoy" thing. When I first got vim introduced / saw from a friend at university. I remember I tried it, he kept saying all good things about it and ended up like you here - thinking "okay just lets use some editor or IDE and get work done"... But guess what? Years later somewhere it was stuck in my mind "it would be great if I learn this properly" and was on a project where heavy text manipulation and non-trivial refactors were a thing. First started using vim in that space, then because I was already on linux anyways, then I installed it in every IDE as a plugin, then I don't even want to use IDE anymore just text editor and terminal and much more productive.

I've been using Vim for 14+, I started when I was at Uni, at that time we didn't have all the plethora of editors that we have today! It's amazing to see so many people using Vim despite how hard is to start using it, it's not very user friendly at all, but if you learn it, you will see the benefits later, It's like start a KZread channel, it's hard but you will see the result later! ;)

@dr.mikeybee

Жыл бұрын

In the 1980s I worked on Unix systems that only had the ed editor. Then vi was a big step up. Then came vim. So of course I learned all the key combinations. Now if a modern editor doesn't have vim functionality, it's slow going. These days I use VSCode with vim emulation. I'm happy to use vim alone a lot of the time, but VSCode has Copilot, linters, and a debugger which are all amazing.

@theodorealenas3171

Жыл бұрын

@@dr.mikeybee that's nice. But why haven't you added that functionality to Vim? It's a doable side project.

VIM is not about getting things done, it's about slacking off. If your boss asks you "why didn't you do anything today?" you just reply "I used VIM." Btw there is a better VIM for macOS, it's called MacVim. You should check it out. Also NeoVim is pretty cool too.

"I don't know why I am happy about this" HAHAH

"He is using an IntelliJ plugin that simulates vim?" Vim-Plug: Welcome, nice to meet you.

I use Vim as a Plugin with intellij for 3 months. And I totally got used to it. I love it and I found myself more and more using Vim instead of my IDE

Not quite what I expected. There might be a different layers of plugins and powertools, as in vs code, that you need to pre-install in vim to make it better, and there is emacs if you want further down that rabbit hole. So I wouldn't say that is a good coverage of things? But fun video anyway...

So I found the Keyboard is actually faster when coding, but had the same challenges with VIM, but I really liked a lot of the vim motions, which make you faster than your mouse. The jumping to the begging of words end of words, inside brackets, etc. I found the best of both words, there are vim motion plugins for VSCode that let you do the jumping around with the keyboard.

"I tried Vim" now do it again for 10 times then you'll start getting the juice

Im a DevOps engineer and im using both vim and VScode. VScode is nice to work on projects. And vim is great to edit one-two files in terminal, especially on a remote computer.

I use Helix, which is like vim, but with different bindings, and more features out of the box!

I tried using Microsoft VS Code (or its open source equivalent) and found I spent too much time clicking with the mouse rather than being able to use keyboard commands. After a month I returned to vim.

I "needed" to learn vim. I wanted to develop stuff but only had an iPad with the shell "iSH". My setup was scuffed as heck: My Up/Down Keys were broken so I needed to use the ones onscreen; I didn't know about multiple file editing so I just closed and opened files with ':x'; My build times were horrendous; But I still managed to code something in the end and now helix, an editor similar to vim, is my main one.

To get features like syntax highlighting, autocompletion and linting you need to install plugins. Also there are no projects in vim, you can just open a file then open another one with `:e` or `:tab split filename`. Note that if the feels lengthy for you, you can and are encouraged on vim to make keybindings and shortcuts to make everything faster

Thanks for the Laugh Alex - been a looong time since I've seen a Windows user (Mac?) try to learn vi. LOL. BTW it's a piece of software written by Bill Joy in the 1970s and is great for editing text files with regular expressions. Other than that I no longer have a use for it. But if you're a UNIX admin you need to know it since every version of UNIX since the 80s has had a copy. I'll stick to Xcode or Visual Studio, for coding Thank you. Cheers

"You should be able to work on multiple files" I mean, you can, but you're also talking about a text editor that's been around longer than the advent of cursor keys, which is why the default movement keys are H, J, K & L, and I do use Vim. I relearned it this past Summer after about 20 years here, when I decided to pick up BASH scripting again (same timeframe).

The key to using vim is learning a few basic commands at the outset and mastering them before learning another group of commands. 1. How to exit the text editor 2. How to insert text and delete text 3. How to move to the beginning and end of a buffer 4. How to move to the beginning and end of a line, and move forward and backward between "words" 5. How to copy one or more lines and paste those lines elsewhere in the buffer 6. Keep learning based on your requirements, not every command supported by the text editor

I decided to learn vim before I even started working. I took the time to do it properly. I just focussed on that for a month. Watched all the tutorials, installed all the plugins I wanted, set up a bunch of custom key binds etc etc. By the time I started my first coding job I was already proficient. I would never be able to invest time like that now that I'm working properly but I'm sure glad that I did it back then. It's probably saved me 20X that time over the years.

The idea is that you don't need to move your hands around the keyboards. That's why you don't have to use the arrowkeys.

I use the VSCode Neovim extension instead of the one you installed in the video. I tried both, but I found the VSCode Neovim plugin to be more responsive. It requires Neovim version 0.8.0 or greater.

When I started programming, I used a terminal connection over an RS232 network. Vi was the tool that was used on Unix boxes to edit files. Now I use vi when connecting over ssh, but that is all. VSCode and IDEs are the modern way, and I'm sticking with it :-)

Btw, you have vim and openbsd microemacs installed by default on mac

I'm left handed, I love VSCode, don't use Vim, but I learned to do a LOT of things with my right hand that I cannot at all do with my left. It saves me a lot of time. It's still just using one hand though.

I've been using Vscode Vim for more than a year probably and it's awesome. At first I was scared that it would decrease my productivity at my work because of clumsiness, but now it feels weird not to use it. Of course, having it as a Vscode plugin means that sometimes I cheat and use the mouse to make my life easier 😅. Now I'm trying to fully switch to Neovim, but syntax highlighting doesn't seem to work very well with TypeScript generics.

Been there…tried vim (because I saw a fellow developer flying across the keyboard developing and angular app). What I learned is…I like VS code…and I am ok with that. To those that use VIM, I salute you…but just because you can does not mean you should 😮

I’ve also started using vim and haven’t stopped since because I dont know how to exit vim

Yes, I use Vim. There is one primary reason for me, and that is you can access and edit files though a login session to a remote server. There are secondary reasons like not having to reach for a mouse and access to shell comands. It is a steep learning curve, but it has the powers; stange powers.

That was very intertaining. Thank you so much. But when you've mentioned pressing F12 to go to declaration -- oof-badoof, what a hustle. Space+gd is way easier. Vim allows that.

For all the great things about vim, I felt like rather than learning to program you end up learning vim.

Did you really have to install vim? I'm still on an ancient Mac with Catalina (macOS 10.15.7) and I'm pretty sure that vim was included with macOS.

Vim does not make you faster always, but makes processing text more pleasent. HJKL keys combined with other vim-movements works surprisingly well if you do not use mouse. I switched to vim years ago because I was tired to use mouse to navigate in a code and any professional IDE that time were too bloated and so slow on my PC.

My story - Used sublime for primary coding, and moved to VSCode post that. while tinkering on servers, I used nano and then moved to vim since nano didn't seem to stand out and I felt it was no harm trying out vim. I got pretty good at vim but mainly for coding I used VSCode. A year ago added a vim plugin to VSCode and that has been the best stuff ever.

Nice video! I have done the vimtutor followed by Drew Niels Practical Vim Once you get used to doing things the vim way, everything else feels more awkward than your ear scratching analogy You have to invest time to learn how to use the tool, but just like a chef chopping an onion without even looking, Vim enables you to do precise cuts of text just by thinking about them. Sure you could chop an onion a million ways, but the most efficient one takes upfront investment to learn the proper tools.

@AZisk

Жыл бұрын

thanks. the chef using a knife is a great visual!

@nodidog

Жыл бұрын

Vimtutor followed by Drew Neils book is the route I would recommend to someone starting out, too! The book is excellent. You can dip into it and learn a few tips every day, it only takes a few months to build up a really good knowledge.

When you enter vim, vim enter you.

Tester here. Also forced to work with vim especially on the devops part... On some of our Linux based machines only Vi/vim is available. We don't have anyone to do the devops stuff so it's up to us to maintain everything so.. vim it is. I still feel like I just use basic navigation for editing, and google lots of things for it. Mostly because it's not my absolutely everyday editing tool, my experience is not enough to be a keyboard vim warrior. Also the dev/team manager loves it so no changes in nearest future i guess

Seems that escaping was not horibly hard. I will try it as well. So far I hold back because heard that it is almost impossible to get out of the Vim :)

@AZisk

Жыл бұрын

i already forgot how to do it 😂

Theres a foundational module in my college that forces us to use Vim 😢. (Exams are taken in vim)

Vim always coming handy when I stuck in the server, but if I in my personal computer, vscode is still good option(dont forget to install vim add on in vscode, hahaha)

I would suggest starting with a Vim plugging in your IDE of choice. For my work i use Rider and for alsmost a year i use IdeaVim. Just recently I started playing with NVIM and configuring all of it with plugins to create something i prefer. But that is more of a hobby project in the evenings. Just the vim layout even with other IDE's has helped my productivity hugely. The way you work with commands to do stuff, and yes also navigating with hjkl, is becoming more natural. You do definitely need to learn to type efficiently with all fingers.

@alexbecar977

Жыл бұрын

I have a personal license and use rider with idea vim and its godlike with relative numbers, imo idea plus vim plugin is the way to go, unless you just need to edit files on server or basic text documents.

You need to use Neovim

I love VIM, I used it in Android Studio, AppCode, etc.

Vim is great for masochistic coders or if you are working on a server and there is no GUI; VS Code all the way.

@AZisk

Жыл бұрын

It certainly feels that way at the beginning.

Vi (or vim) is not supposed to be a substitute of a full IDE environment like vscode. But it is a very powerful text editor that is always available on a *nix machine, no matter how you've connected on it, regardless of being on a gui or a terminal mode. It has endless capabilities hidden in those shortcuts, however its true power is that it is always there when you need to edit a configuration file or change something on the OS and you can always run it even if you have only a black and white terminal available.

In addition to Alex and TJ below: The reason for "why not the arrow keys" is that vi, the "vi" in "vim" - that is "Vi IMproved" - is from days when you'd use terminals that, you guessed it, does not have arrow keys. So basically, through the history of "vim" (vi -> vim -> neovim, and that there is me starting a religious war) there's a continuum of people already being used to hjkl being "the way". Incidentally, you can see the same in a lot of tiling window managers on Linux and some things like Yabai on Mac. (Fun fact: I don't miss arrow keys - my desktop's keyboard does not have them. So much space saved on my desk! :D ) Further to that, I rarely move around with hjkl directly. Instead, you use combinations. For example, if I want to go to a letter 10 steps to the right, I type 10l. If I want to go five lines down, I type 5j. This is the power when you get used to it: want to delete 4 words? Instead of grabbing the mouse, click-drag, press delete, I just do: d4w. ("Delete 4 Words") Boom, gone. I want to "yank" (copy) 5 lines? V5jy (capital V to select whole line in visual mode, 5 lines, j for down, y for "yank"). Boom, done, I have copied it. If I want to cut them: V5jd (d for delete, but also stores it in "clipboard") I want to delete a whole line? dd Done. So basically, it's not stupid or arbitrary, it's just "very old" in some respects, and completely counter to what a lot of people have grown up expecting in the 46 years since VI was designed. (I'm old enough that command line was default when I started using computers.) On laptops especially, I love this, because I just can't with touchpads. VI (though I use neovim, usually through the lunarvim distribution) lets me work on my code efficiently without having to pack a mouse or give myself RSI through using the touchpads. All the other nice stuff (language server protocols, blah blah etc) are there through plugins - or in my case, just installing lunarvim. I'll not go as far as say "vi/vim/neovim is superior" to Vs Code or whatnot. But _for me_ it is. For most people? No. And if you want a real ride: install the "vim mode" plugins for Firefox so you can navigate websites without your hands ever leaving your keyboard.