4 ms·
> Moreover, the rarity of projects using Remote X, or abstracting it with libraries like NoMachine kinda validates the idea is the feature is considered a novel
by misnome 4y ago
> Moreover, the rarity of projects using Remote X, or abstracting it with libraries like NoMachine kinda validates the idea is the feature is considered a novelty and not used much.
> While I like the feature, I have feeling that it won't be missed or sought after much.
It’s not used or won’t be missed _by you_. It’s extensively used today by science and HPC facilities and clusters, where it’s at best complementary to things like NX (with the problems of basically having a second desktop instead of integrating into the existing system), but often the only option for remote GUI to heavier duty systems available, not to mention the remote OpenGL capabilities which although out-of-date and clunky, allows more efficient local rendering than just streaming bitmap deltas.
- bayindirh 4y agoAs an HPC cluster administrator, I (and my colleagues) don't see its use on our clusters, either. Instead, researchers either post process their data in the user interface and download it to visualize, or get the raw results and post process and visualize in their systems. Once in a blue moon, a user generates some output window which requires very few interactions to look at their preliminary data, that's all.
- mbreese 4y agoYeah, I’m an HPC user (and small cluster admin by necessity). Remote X11 windows haven’t really been common for years. Occasionally you’ll see an Rstudio server instance, but this is tunneled through an SSH port forward and uses HTTPS. The last time I needed and X11 remote session in a cluster, it involved Matlab and some kind of toolkit. The performance of using a GUI remotely is nothing compared to just copying a terminal figure through an SSH tunnel and viewing the figure locally. I’d say that the low performance of remote X11 was the biggest factor in this shift.