|
|
|
|
|
by wmccullough
3000 days ago
|
|
This is true for me :( I'm a career-long .NET dev and I've wanted to step away and begin learning C++ on a non-Windows platform with VIM and my only attempts were met with so much frustration that I gave up. To be clear, I believe in the power of VIM, I just never got acclimated to it. Maybe this year is the year I stop making excuses and just learn. P.S. I see lots of arguments elsewhere about whether VIM is an IDE. Either way I think your first point stands in my case @oblio. |
|
Use dotnet core on Windows, with Visual Studio.
Use dotnet core on Windows, with Visual Studio Code.
Use dotnet core on Linux, with Visual Studio Code, etc.
Then maybe try dotnet core on Linux, with Vim.
But don't believe the hype. I use Vim as an editor because I do a lot of scripting. I use it even on Windows. But I use it because I'm already used to most of its commands, I have a decent config file for it (somewhat lean, not that many plugins) and for my job I need to know it cause I often interact with various systems which use it.
Despite being a touch typist and knowing most of the commands, I'm still a Vim heathen. That is, I don't use numbered yank buffers, I just use the default one, I also remapped Ctrl-c, Ctrl-v to do visual block operations for when I'm too lazy to come up with fancy selections, etc.
Anyway, my point is, using Vim might not pay off fully. My brain just isn't wired to work in Vim commands. And I know and use w, W, b, B, f, t, folds, blah, blah. I definitely don't use it to "magician" level.
You know what? I think in the end it doesn't matter. The only time Vim's nature actually helps is when I pre-process some sort of text data dumps.
For the other moments I'm thinking way more than I'm writing or editing. So it's not the text editor that's the blocking point.
Damn blocking IO. Getting outputs from the brain is hard and slow!