3 ms·
I had to work for a week on my gaming PC and used virtualbox to run Linux in a VM with i3. It was really sad, I hope to never do it again. No matter what termi
by doix 5y ago
I had to work for a week on my gaming PC and used virtualbox to run Linux in a VM with i3. It was really sad, I hope to never do it again.
No matter what terminal emulator I used, there was too much lag compared to the real thing. I couldn't use kitty/alacritty since there was no hardware accleration. When I'm looking through code in (neo)vim, I normally fold everything and then scroll by holding j/k. I set my repeat delay very low, and my repeat rate extremly high so that I can just quickly scroll through code. This was completely unusuable in a VM. I had to switch to ctrl+f/b/d/u and it drove me nuts.
Maybe there was some way to get better hardware accleration, if I had two graphics card, maybe I could have devoted one to the VM and gotten better performance. Or maybe virtualbox is bad vs vmware or whatever else is out there.
I'm sure if I had to use it long term, I could come up with some usable workflow, but I still think using it natively is a significantly better experience.
- doubled112 5y agoIs there too much lag through an SSH connection for you? I often do things this way. SSH from whatever I'm holding to a more powerful machine with my tools and configs. Then the terminal is on your host, at least. I've also RDPed into local Windows VMs to get a better experience like working copy/paste. That's the approach Hyper-V took with their enhanced session mode
- movedx 5y agoSorry to hear that mate. It's been fine for me. I'm not that overly sensitive to millisecond delays in rendering or response times, so it works out fine. Ryzen 3 9600X, 32GB of RAM, nVidia RTX 2080 Super on a 49" G9 Ultrawide, for reference.