4 ms·

Was getting a bit into VIM and Tmux earlier this year but then my linux environment fell apart and I had to switch to Windows as a hypervisor. I really want to

Was getting a bit into VIM and Tmux earlier this year but then my linux environment fell apart and I had to switch to Windows as a hypervisor. I really want to learn so that when I start working on headless servers I can have a consistent workflow (nano seems a bit to... novel for me, though I know some people here prefer to use that for all of their text editing needs). I'll have to come back to this when I'm done with making things.

hesdeadjim 4y ago
You tried WSL 1 or 2? I'm a Windows gamedev and I do all my coding in Neovim under WSL 1. If you are curious about which version to pick: * WSL 1 - OS-level API translation layer, access to mounted Windows filesystem is decent performance. Can't run Docker inside the container. * WSL 2 - Kernel layer integration, abysmal Windows mounted filesystem performance, essentially "real" Linux, can run Docker natively.
- 7speter 4y ago
  I'm using Fedora on a VM. I'm working with angular and it's CLI works VERY slowly with WSL2 for some reason.
  - AlchemistCamp 4y ago
    WSL2 is slow working across the Windows-Linux bridge. If your project files are in the Windows part of your system, I'd strongly suggest moving them to the Linux filesystem. If that's not an option for some reason, then you're better off with WSL1.
  - Kwpolska 4y ago
    You’re probably using the Angular CLI within the Windows filesystem via WSL2. This tends to be slow, because all your file accesses go through various indirection layers, and that quickly adds up when you’re dealing with thousands of small text files (as you usually are in the JS world). There are two alternatives: 1) working directly with Windows, where Angular CLI and many other things should work just fine and with nice performance, 2) working on the Linux filesystem inside WSL2 (i.e. outside of /mnt/c/), which is a disk image (.vhdx) using ext4 mounted directly in the VM.
- Kwpolska 4y ago
  For neovim, I’d consider the native Windows version, it works pretty well for me. Another argument to pick WSL 2 would be the fact that it gets all the love and support from Microsoft, and all the cool new features (eg. Linux GUI support).

hesdeadjim 4y ago

You tried WSL 1 or 2? I'm a Windows gamedev and I do all my coding in Neovim under WSL 1. If you are curious about which version to pick: * WSL 1 - OS-level API translation layer, access to mounted Windows filesystem is decent performance. Can't run Docker inside the container. * WSL 2 - Kernel layer integration, abysmal Windows mounted filesystem performance, essentially "real" Linux, can run Docker natively.

7speter 4y ago
I'm using Fedora on a VM. I'm working with angular and it's CLI works VERY slowly with WSL2 for some reason.
- AlchemistCamp 4y ago
  WSL2 is slow working across the Windows-Linux bridge. If your project files are in the Windows part of your system, I'd strongly suggest moving them to the Linux filesystem. If that's not an option for some reason, then you're better off with WSL1.
- Kwpolska 4y ago
  You’re probably using the Angular CLI within the Windows filesystem via WSL2. This tends to be slow, because all your file accesses go through various indirection layers, and that quickly adds up when you’re dealing with thousands of small text files (as you usually are in the JS world). There are two alternatives: 1) working directly with Windows, where Angular CLI and many other things should work just fine and with nice performance, 2) working on the Linux filesystem inside WSL2 (i.e. outside of /mnt/c/), which is a disk image (.vhdx) using ext4 mounted directly in the VM.
Kwpolska 4y ago
For neovim, I’d consider the native Windows version, it works pretty well for me. Another argument to pick WSL 2 would be the fact that it gets all the love and support from Microsoft, and all the cool new features (eg. Linux GUI support).