3 ms·
The painful part of that setup is that all the tools you want to use on the source code must either run on the server itself, thus installed somehow, or some sl
by tored 2y ago
The painful part of that setup is that all the tools you want to use on the source code must either run on the server itself, thus installed somehow, or some slow remote mounted filesystem, this severely limits the tools you may want to use.
- trog 2y agoWhat tools don't run on Linux? Modern tooling almost assumes Linux in most cases now. As a Windows user I feel like I hit this wall way more often than any other.
- tored 2y agoRunning an IDE over ssh or samba is just an awful experience, but generally if I want a command line tool to be installed I need to be either root or I need to ask the administrator of the server to install it, on my own machine I can install whatever I want and I can run whatever operating system or distro I want. And if I'm traveling I can bring my laptop with me, can't do that with a server.
- trog 2y agoOh right sorry I did forget about that aspect. I haven't done that for a while with a big codebase with, say, VS Code, and not on anything that wasn't very low latency (sub 10ms, so local LAN). I am mostly editing directly on the server when I do it these days but that wouldn't fly for anything other than the light hacking I do.
- tored 2y agoThese days with many working on remote location you also need to include the VPN latency.