![]() ![]() The same argument applies here too: that time is cumulatively increasing my skill at the tool rather than getting to the same point with various tools (cf the old interviewing dilemma: does this person have 5 years of experience or 1 year of experience 5 times). Now I'm one of those folks that likes to master my tools and craft my own tools as well, so I've continued to invest time in my vim mastery. That time adds up to be more than my initial vim investment. They all have to put time and effort into getting comfortable and proficient in each of these environments. In the same time period, I've watched plenty of my cohort jump between IDEs and "modern" editors as they come and go (jetbrains, visual studio, textmate, sublime text, vscode, the various storm ides, etc etc). It's an up-front cost yes, but I see it similar to a carpenter learning to use a hammer - it's a skill that carries forward for at least a quarter century. I still have stuff in my config from that time period, that still just works. If you value your time that way, you should re-consider (neo)vim. I really wish I could share with you the joy of tinkering, learning, and growing your knowledge about how these wonderful machines work. Then again, I suppose some people are just here for the money and want to clock in and clock out as fast as possible. I recently setup Emacs and got it to the same level as my Vim usage in about two days of tinkering just for fun. If dumb college me can do it in a few weekends, you can do it. I personally consider my investment into Vim one of the best I ever made. I guess it's the systems developer in me that can't fathom someone that wants to use a tool to make a living without understanding it fully and being able to tweak it to their exact liking over the course of their entire career. I really don't understand the comments of "I will literally not spend a single minute configuring my editor". So I get 98-100% of what an IDE gives me, I can use my editor over ssh and edit anywhere, I don't need a GUI to even be installed on the system where I have all of my cores and RAM for compiling the kernel, it starts up instantly, and it's completely free and open source, not driven by a corporation, and there's decades of documentation on how to use it. ![]() I am very glad that neovim is also making things EVEN BETTER with tree sitter and baked in LSP support. With term added (which is a core Vim feature) it also has excellent support for gdb debugging. I can edit the kernel with clangd and get hover reference, autocomplete, go to def, ref, dec, smart refactor, and that's on top of being able to easily jump and fix lint/bugs using Vim's already great support for parsing compiler errors. I will never understand why people choose VSCode/Jetbrains over a terminal based editor.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |