Ok we get it, vim keybindings are cool and all. But why would you use an ancient, deprecated text editor that lacks all the modern features every employed software developer needs? You do realize these keybindings and modal editing exist as plugins for every IDE worth using?Time to stop being a trooner and start using a white mans development enviroinment. This is what peak performance looks like.inb4 you only need vIMbRo>best debugger on Windows (builtin)>Best C/C++/C# development experience on Windows>Win32/NTAPI/WDK headers
>>109112521why make this thread three times
didnt you make this post yesterday
>>109112521you only need vIMbRo
It's called doing it because you like it not because you want the end product
>>109112521>modern features every employed software developer needsSuch as?
>>109112980AI
What if you are not on Windows? Maybe Linux like most of programmers? Vim is lightweight and fast. Don't make me start.
I code in notepad++/Kate
>>109112559He did. Also>>109112521>Ok we get it, vim keybindings are coolLMAO wtf, who told you that? Nobody uses vim, it's some late 80s shit, it was hated back then, a literal malware and a prank software that makes you read manuals to turn it off and purge it from the system. You can't be serious about vim in 2026, right? Right?
>>109112521I'm not a coder but I am a sysadmin and I prefer vim because a lot of keybindings for movement within vim are shared by other important tools like less and more importantly man pages.Plus vim shares a lot of concepts with bash like how the $ sign is used for 'end of'.So for sysadmins dealing with bash and lots of terminal stuff, what you learn in vim transfers over.Plus vi exists in pretty much every remote server on earth so you don't need to rely on your own text editor and your own configs when needing to just do quick scripting or modifying config file.
