2.7 KiB
| author | link | date | rating | image |
|---|---|---|---|---|
| twitter:nikolalsvk | https://medium.com/swlh/ultimate-vim-typescript-setup-35b5ac5c8c4e | August 2, 2023 | ⭐⭐ | Media/articles/images/ultimate-typescript-vim.jpg |
Ultimate Vim TypeScript Setup. How and why to use Vim for TypeScript… | by Nikola Đuza | The Startup | Medium
#technology #coding #text-editors
Vim is great. I have been using different text editors and IDEs through years, and Vim stuck with me through all hardships and happy times. Maybe because I invested much time in learning and fine-tuning it to my needs that it became a part of me, a bit.
I love Vim. It’s not easy to use. I love Vim anyway.
Maxin Cardamom
With those lines, one of the best Vim talks on YouTube starts. And it makes perfect sense. I remember being frustrated and asking why would anyone use Vim while I was learning it. But all that paid struggle off. If you are afraid of the Vim learning curve, I found this great post that proclaims you can learn Vim 30 minutes!
One of the main reasons why I use Vim as my editor is speed. And I do not mean the speed of writing code, which is also excellent. I am thinking of the reading speed of the code. Did you know that the ratio of reading versus writing code is 10 to 1. That means that you are regularly reading old code to write new code. And with Vim, reading and finding old code has been the easiest and fastest for me!
I will explain in another blog post which plugins and shortcuts I use, so be sure to subscribe to the newsletter.
VSCode vs. Vim
A lot of folks are using Visual Studio Code for development. I do not blame them. I have used VSCode and Visual Studio and it is one of the best software that came out of Microsoft!
Most recently, I have been using VSCode for writing (and reading) TypeScript code. Why you’d ask? Well, before I made an ultimate Vim TypeScript setup, I had to use VSCode. The only reason why I used VSCode, was that Vim was too slow for editing TypeScript files.
Luckily, I have upgraded Vim to 8.2 version, and it started to be blazing fast once again. I ditched VSCode and moved back to Vim and my .vimrc.
If you are thinking about the two, I would say to use Vim, but I am probably biased. VSCodeVim lets you combine the best of two worlds…