space_comrade [he/him]

  • 0 Posts
  • 79 Comments
Joined 4 years ago
cake
Cake day: November 11th, 2020

help-circle
rss




  • space_comrade [he/him]toLinux@lemmy.mlHow to quit VIM?
    link
    fedilink
    English
    3
    edit-2
    7 months ago

    Just switch to VSCode or something similar, it has enough features and shortcuts that will quickly make you like at least 80% as productive as you were in Vim. It even has a Vim mode so you can wean yourself off of it more easily.

    Honestly never got the appeal of Vim, you need to spend so much time learning and configuring it only to squeeze out a little bit of extra productivity out of it when compared to a “normal” editor/IDE. I don’t see why it’s so important to be able to edit and write code as quickly as possible since most of the time you’re going to be debugging or looking at the code or reading docs.

    EDIT: Just noticed you said you don’t code a lot. I think most of what I said still applies, I imagine you don’t spend 99% of the time in the editor typing away.











  • For what I see as a helpdesk guy, most problems that are encountered origin from Windows being Windows, not tech knowleadge of some person.

    Yeah but things just work by default more often on Windows than on Linux. “Linux being Linux” is also the most common cause of Linux problems.

    Linux usually does give you the tools to fix problems more easily than Windows but that’s where the tech savviness comes in.




  • I don’t like VMs because I need to allocate memory upfront for it, and considering it’s a Windows VM and depending on the dev work you’re doing on it you might need to give it 10Gb+.

    If it’s at all possible for OP I’d recommend getting a separate physical workstation and then just remoting into it with your Linux machine, if you use VSCode the process is pretty much seamless, you use VSCode from your Linux machine normally while all the work is being done on the remote machine.