3 ms·
I made a concerted effort to learn Vim maybe a year or two (the last 3 years scarily blend together for me) ago and, while I enjoyed it, I moved to Windows and
by 7speter 3y ago
I made a concerted effort to learn Vim maybe a year or two (the last 3 years scarily blend together for me) ago and, while I enjoyed it, I moved to Windows and instead of trying to carve out a vim workflow, I just resorted to using VSCode. I used mostly freecodecamp tutorials to learn about setting up Vim back then.
I haven't been doing much coding (and I don't think theres much support for Angular and C sharp/dotnet, which is where I left off), but getting fluent in the Vim workflow is on my bucket list.
I never see it ever spoken about from this perspective but its sort of like learning how to drive stick, where you're able to drive anything: if you learn vim, you can code on any computer made in the last 15-20 years, potentially preventing old machines from ending up in a landfill, or allowing you to viably code on the tiniest singleboard pcs without having to worry about whether you're gonna hit the ram limit.
- mekster 3y agoIt's about working on a remote server. Use whatever GUI editor you wish for local use. VScode can also work on remote files but not as flexibly as running vim on the server side.
- langfan 3y ago>I never see it ever spoken about from this perspective but its sort of like learning how to drive stick, where you're able to drive anything: if you learn vim, you can code on any computer made in the last 15-20 years True. That's roughly what it says (in other words) in the blurb for this vi quickstart tutorial, and why it is quite applicable for the purposes you said: https://vasudevram.gumroad.com/l/vi_quick https://vasudevram.gumroad.com/l/vi_quick