←back to thread

90 points sugarpimpdorsey | 7 comments | | HN request time: 0s | source | bottom
1. PeterStuer ◴[] No.44775133[source]
Running a remote VScode backend on those while it is technically using the traditional shared server feels like that is not for the "shared" part but just because it is free and available?
replies(1): >>44775241 #
2. zevon ◴[] No.44775241[source]
Free and available is always good (especially in a research environment). ;) The author also says this in the P.S.:

"I believe the reason people run IDE backends on our login servers is because they have their code on our fileservers, in their (NFS-mounted) home directories. And in turn I suspect people put the code there partly because they're going to run the code on either or both of our SLURM cluster or the general compute servers."

replies(1): >>44776073 #
3. bravesoul2 ◴[] No.44776073[source]
Wonder why they dont use git. Maybe a lot of that isn't committed but is large data files?
replies(1): >>44776179 #
4. dkdcio ◴[] No.44776179{3}[source]
that’s orthogonal, right? they may or may not be using Git regardless of where the files are
replies(2): >>44776829 #>>44780166 #
5. kfichter ◴[] No.44776829{4}[source]
I use VSCode's remote/ssh functionality all the time, particularly when I need to develop code on an environment that's more capable than my local machine (or when my internet is weak). Still use Git, no reason why you'd change that when working on a remote machine.
6. bravesoul2 ◴[] No.44780166{4}[source]
I mean rather than work off a remote machine for the convenience of having files you can deploy to a compute cluster use git (or maybe scp) to work local and then deploy them when needed. For a lower latency editing experience.
replies(1): >>44783107 #
7. PeterStuer ◴[] No.44783107{5}[source]
Honest question. Do you experience subjectively observable latencty differences when editing local vs over the lan?