4 ms·
Try using VSCode in terminal mode when you're logged into a remote machine via SSH and see how well that goes. > It's slow (I have i7 with 4 cores and 32Gb of
by peterkelly 5y ago
Try using VSCode in terminal mode when you're logged into a remote machine via SSH and see how well that goes.
> It's slow (I have i7 with 4 cores and 32Gb of RAM)
Something is wrong here. I can't remember the exact specs of the machine when I first started using it but it might have been as low as a 486 with 1 core and 32Mb of RAM.
- vbezhenar 5y agoThat's because Emacs is web scale.
- loxias 5y agoYeah, the first machine I started using Emacs on was similarly spec'd, and it's only gotten faster since....
- kamaal 5y ago>>Try using VSCode in terminal mode when you're logged into a remote machine via SSH and see how well that goes. On the other had vscode is the best experience I've had editing files remotely. Unlike emacs where you have install and configure tramp. The experience in vscode was seamless. In fact the Python vscode plugin is clever enough to understand you are opening a remote python project. It will ensure the local venv is set up with all your tooling(flake, black etc) None of this possible with Emacs. Emacs gives a good editing experience. But we have moved one from coding being merely a text typing excercise.