Remote Workstations for the Discerning Artists

1

Jump Desktop

I work on Jump Desktop (<a href="https://jumpdesktop.com" rel="nofollow">https://jumpdesktop.com</a>) that's being used for remote video editing @ 60fps on up to 3 monitors. It supports very low latency remote desktop and even works in environments that have high latency. For example here's Jump connect from the East coast to a physical server in Paris with 150ms ping times: <a href="https://twitter.com/jumpdesktop/status/1356679263806763013?s=20" rel="nofollow">https://twitter.com/jumpdesktop/status/1356679263806763013?s...</a><p>It works on Macs and Windows.

#Remote Desktop #Remote PC Access #Remote Control 16 social mentions

2

NixOS

> a better alternative would instead be something akin to Dockerfiles where you assert what packages you want to be installed on top of a base system, and if you want anything changed you update the dockerfile and rebuild the whole shebang.<p>Something like Packer?<p>You are right that there are hidden pitfalls. But they shouldn't be a great deal if servers are cattle. A lot of corner cases are related to trying to manage servers that live forever. This shouldn't really be done in 2021 except in rare cases.<p>> I'm imagining a system where the local filesystem is more or less immutable and work is saved to separate filesystem<p>CoreOS worked like that. Immutable filesystem for the system itself. It also had a secondary "mirror" of this filesystem that was used for upgrades (and as a fallback in case boot failed). New stuff would either come when the instance first booted up (cloud-init), or via system upgrades.<p>They were acquired and so my experience with them ended there.<p>There's also <a href="https://nixos.org/" rel="nofollow">https://nixos.org/</a>.

#Front End Package Manager #Package Manager #Linux Tools 246 social mentions