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.
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