Each tool has its own set of ups and downs. In the case of Text Editors, Vim is good for code maintaining i.e, where you do more updations than writing something new. But, when we are building something from the scratch, we might need more third-party support and GUI intensive workflows, that's where using Vim is not a good idea.
It depends on the situation and the environment. Let's say you are a freelancer, most probably you'll be creating different new projects. If you are working in a Company, it's highly probable that you'll be maintaining the codebase.
My conclusion is to, use the right tool for right work.
Thanks. I see: I just never saw "editing" as separate from "coding" or that "coding" only meant when it was written the first time.
To me it's just all coding and all editing.
Personally, I used to be a vim power user, and I'm still glad I learned it and still use it very often. However, as my primary editor, VS Code has really taken over for me.
Compared to vim, with VS Code I've never lost a file or even a single edit, I don't have to mess with swap or backup files.
But like others have said, they're tools. They're not religions. Pick the best for the situation and there's no harm in learning something new.
I have built a number of things from scratch, including but not limited to, a couple of compilers, an UI library in react, few websites end to end, few web services, a number of fun side projects; I have done a number of freelance projects during my time in college too. I have never needed anything more than a terminal (guake on my Linux machine and iterm2 on my work laptop) and a browser (chrome only. I use browserstack for testing/previewing on other browsers). Vim has been an integral part of my Dev setup. It may not have all features of a modern IDE, but it's best at what it does-- text editing. For all other features that I need in my workflow, there is always a CLI tool that specialises in that. Even though I have tried multiple IDEs over the years, I found that the only useful thing that comes out-of-box with IDEs is static code analysis. This is the only thing that doesn't come with vim out-of-box, you need plugins for that. Most of the useful text editing features in modern IDEs are present in vim or covered by some plugin. Also I found that autocompletion in other IDEs feel fancier, but it's generally faster to write code without autocompletion as long as you are a decent typist and know what you're doing; also if your class, method and variable names are so verbose that autocompletion is faster than typing them out, then it's an indication that you need to reconsider the way you're naming stuff.
Each tool has its own set of ups and downs. In the case of Text Editors, Vim is good for code maintaining i.e, where you do more updations than writing something new. But, when we are building something from the scratch, we might need more third-party support and GUI intensive workflows, that's where using Vim is not a good idea.
Yeah, vim really is made for editing. But really most developers spend more time editing than coding - at least I do
"But really most developers spend more time editing than coding"
huh?
It depends on the situation and the environment. Let's say you are a freelancer, most probably you'll be creating different new projects. If you are working in a Company, it's highly probable that you'll be maintaining the codebase.
My conclusion is to, use the right tool for right work.
I mean we usually type out our code then spend a lot of time running it, and tweaking it and debugging it right?
At least it applies to me
I mean we usually type out our code then spend a lot of time running it, and tweaking it and debugging it right?
At least it applies to me
Thanks. I see: I just never saw "editing" as separate from "coding" or that "coding" only meant when it was written the first time.
To me it's just all coding and all editing.
Personally, I used to be a vim power user, and I'm still glad I learned it and still use it very often. However, as my primary editor, VS Code has really taken over for me.
Compared to vim, with VS Code I've never lost a file or even a single edit, I don't have to mess with swap or backup files.
But like others have said, they're tools. They're not religions. Pick the best for the situation and there's no harm in learning something new.
You can checkout my ~/.vimrc here: github.com/valbaca/dotfiles/blob/m...
And my "virc" which is a more minimal vimrc here: github.com/valbaca/dotfiles/blob/m...
Yeah the swap file thing is real. It's happened to me a few times
What would be an example for a GUI workflow?
What do you mean?
I have built a number of things from scratch, including but not limited to, a couple of compilers, an UI library in react, few websites end to end, few web services, a number of fun side projects; I have done a number of freelance projects during my time in college too. I have never needed anything more than a terminal (guake on my Linux machine and iterm2 on my work laptop) and a browser (chrome only. I use browserstack for testing/previewing on other browsers). Vim has been an integral part of my Dev setup. It may not have all features of a modern IDE, but it's best at what it does-- text editing. For all other features that I need in my workflow, there is always a CLI tool that specialises in that. Even though I have tried multiple IDEs over the years, I found that the only useful thing that comes out-of-box with IDEs is static code analysis. This is the only thing that doesn't come with vim out-of-box, you need plugins for that. Most of the useful text editing features in modern IDEs are present in vim or covered by some plugin. Also I found that autocompletion in other IDEs feel fancier, but it's generally faster to write code without autocompletion as long as you are a decent typist and know what you're doing; also if your class, method and variable names are so verbose that autocompletion is faster than typing them out, then it's an indication that you need to reconsider the way you're naming stuff.
Woah, you've built a lot of stuff