![]() ![]() The most powerful position is to be master of both (via tools like ViEmu), where low level text manipulation is done via Vim's editing model, and semantic manipulation is done via IDE tools. Note, that people with strong mastery of good IDE tools, like Visual Studio + Resharper, can do similarly mind-blowing shit at a higher semantic level via templates and refactoring tools. The Emacs editor uses the Ctrl key in combination with certain letters to perform special functions, can be used with the LISP(LISt Processing) artificial intelligence programming language, and supports hundreds of keyboard functions,such as the vi editor. Just get good at Vim and you'll have no need to justify it. Any time I do co-development, or screenshare my development work, people are blown away at what's happening in my editor compared to what they're using to seeing in theirs. ![]() ![]() ![]() I've routinely had people looking over my shoulder say "WTF?", because my editor is doing crazy shit to text seemingly on its own. Unfortunately, if you are logging in to a non-GUI server or into a machine through a text based connection (even if it has a GUI installed), pretty much the. My colleagues very quickly realize that my Vim usage is a super power, not a throwback or liability. Vim's great strength is raw text manipulation, emphasis on "raw" because its understanding of that text, semantically, is generally poor.Įvery time I start a new job or my smug colleagues are like: "huehue, this guy still vims, I havent used vim since college, its 2018 bro". Efforts to close that gap are generally complicated, hackish, and subsequently fragile. IDEs are typically much, much better at this. Vim sucks at understanding your project structure and code. Honestly, I would like some honest answers as to where is Vim lacks or situations I'm better off using a different text editor/IDE ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |