2 ms·
About 3 months ago I went full thin-client using similar internal tools. 90+% of my workflow is using terminals and editors that work brilliantly over an SSH tu
by AlotOfReading 4y ago
About 3 months ago I went full thin-client using similar internal tools. 90+% of my workflow is using terminals and editors that work brilliantly over an SSH tunnel. For the stuff that can't be done on a remote computer (flashing boards, physical hardware), I have a couple scripts that allow me to do that locally. The whole thing has turned out to be less work than the physical tower under my desk.
- surajrmal 4y agoCommon problems in my experience: * Build performance is crap every morning as the file cache is purged from RAM overnight and needs to refetched from remote disks * Build performance is largely determined by how much cpu and RAM others VMs on the server are using concurrently. Sometimes it's really good when it's underutilized, but sometimes it can be pretty bad as you are no longer using more resources than you were allocated * Trying to interact with it via a GUI (chrome remote desktop for instance) is quite laggy. This doesn't bother me as I am already on the ssh + tmux gravy train. I really appreciate the consistency of dedicated hardware and really don't want to give it up.
- Galanwe 4y agoBut we're not talking about the same thing here. I do also work 99% in the terminal, and SSH is perfectly okay. But my window manager is running locally. In a thin client/remote desktop setup the WM is running remotely. From my experience, this makes the mouse and keyboard ever so slightly laggy that's it's very annoying.
- cosentiyes 4y agoI'm under the impression that the vast majority of people use their cloudtop over ssh and a remote vscode connection. I only ever use a remote gui for a few minutes every X weeks to do chrome-based auth for an nonstandard workflow.
- deleted 4y ago[deleted]