7 ms·
I don't know whether you used Remote X, but I used it in a project, and it's extremely inefficient, esp. in thin client applications, and if you try to carry an
by bayindirh 4y ago
I don't know whether you used Remote X, but I used it in a project, and it's extremely inefficient, esp. in thin client applications, and if you try to carry anything like a video, a 100mbps connection could easily be saturated by one pair of X server and client. In other words, it doesn't work in any way unless you have a gigabit LAN.
NoMachine developed a couple of libraries called NX back in the day, which transferred images and image deltas over with high compression. We used this instead via in the same project (with X2Go), and I reimplemented the same stack to my university where 20 something users connected remotely to a single "terminal" server to do remote research, and it worked like a charm.
While I like Remote X, it's still very inefficient even today. So, unless it's made extremely efficient over normal internet, over residential connections, it won't be missed.
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.
On the other hand what killed X is its code state, rather than the complex architecture. It's haphazard development over the years which made the code unmaintainable.
Addendum: Remote X made sense back in the day. Carrying minimal data, mostly terminal windows between terminals and central mainframe/time sharing system, over relatively short distances. I guess it's never designed and considered for long distances like today's internet, hence it's left to the wayside.
- aliqot 4y agoRemote X has been a godsend for me. I'm not always able to lug around a worthy machine, so being able to use lesser hardware as a 'thinclient' to my wireguard'd assets is very handy. Obviously I'm not going to expect high definition video or realtime gaming, but that's not what it's billed as either, so within the scope of what it's for I'm wholly satisfied. People on both sides sound somewhat fanatic, and I've never understood that. I just want to use what serves me best with the fewest interruptions. I ran wayland for 3 years in various forms, and could not reconcile the bumps and stumbles in the process. Maybe next year I'll give it a shot again. There has to be something that it's doing for everyone for me to be hearing this much about it still.
- jacob019 4y agoxrdp is so much more comfortable to use than X forwarding. A PITA to set up though. VNC is a sensible choice too.
- jeroenhd 4y agoI'm so glad modern GNOME has xrdp support built in. It's just a toggle in the settings. My previous attempts to make it work have ruined the standard configuration so I'll probably need to do some serious purging/reinstalling to get it to work, but for new installs I'm sure remoting into GNOME must be a LOT easier.
- aidenn0 4y agoIs it more of a pain to setup then just running freerdp-shadow-cli?
- jacob019 4y agoI use xrdp for headless remote sessions, and vnc for remote access to live sessions. I'll give freerdp-shadow-cli a try, thanks!
- jacob019 4y agoTried freerdp-shadow-cli, didn't work very well. Vinagre RDP client was unable to authenticate at all and just showed a black screen. I only knew that it was an authentication issue due to the server log. FreeRDP client didn't work with my multimonitor setup, it only showed the secondary screen. It doesn't scale the display properly either. The client must be set to the same resolution as the host. I'll be sticking with VNC for screen sharing, and continue using RDP for headless sessions.
- fsckboy 4y agocan xrdp or vnc display individual remote windows on my local desktop side by side with local windows? I don't want to import an entire remote desktop. That's what I've always used X for, with seamless mouse X select and middle button paste. > more comfortable to use than X forwarding. A PITA to set up though. X port forwarding is painless, not sure what aspect you're referring to?
- 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.
- skybrian 4y agoAlso, I suspect that the bandwidth used by a typical X app was far lower back when it was invented. I remember seeing some greyscale X terminals, and probably not many levels of grey either.
- nikau 4y agoA long time ago I used a Citrix xserver that translated everything to ica, it was very fast and hid the latency well even over an isdn connection.
- Rediscover 4y agoBy any chance, was that at Boeing?
- nikau 4y agoNah it was an Australian finance company running some in house trading and market data apps. Would have been very late 90s I think. I remember it was even faster than the Windows ICA apps at the time which I think were hosted on a NT4 Citrix server. Curious to know if Citrix even sell the Xwindows version any more.
- fulafel 4y agoIt's interesting how our networks have gotten relatively much slower. When X11 was designed and for a long time afterwards, networks were fast enough. But now end user networking performance has plateaued much earlier and faster than computing power and app bandwidth requirements. 100M became the norm in the mid 90s, 1G in the mid 00s, but there was no 10G norm in 2010s or 100G norm in 2020s, we're still at almost the same spot of the curve 20 years later. Save for some tragicomic attempts at 2.5G etc end user networks. Part of the reason of course is wireless, apps adapted to flakiness and bandwidth unpredictably alternating between slow and very slow, and also last mile consumer uplinks adapted to this.
- bayindirh 4y agoI think it has two reasons, first the price of the hardware required to do these speeds (plus the cable requirements + range limits), and WiFi. These slowdown is offset by improvements in video and audio codecs, transparent compression and better static compression formats. So, having 100mbps WAN connection at home is arguably provides more utility than having 100mbps 5 years ago. Unless you do professional photo/video work, a 10G connection at home makes no sense. A good 802.11AC network plus some gigabit nodes is more than enough for a nice smooth experience at home, for most people. P.S.: As a sysadmin, I know delights of having a lightning fast network at any place you live/work, but no, I'd rather spend time with my family rather than maintaining that.
- fulafel 4y agoThe price of hardware is a red herring. All the other ethernet hardware was also pricey at start and then with volume became cheap. The cost and volume normally develop hand in hand (into opposite directions). And yes, our apps adapted to working with less bandwidth. We don't know what kind of apps and computing we would have in the alternative universe where the norm would have been 10G connections 10 years ago. For example lots of P2P stuff has been badly hampered by performance problems resulting in the centralization of the net in hands of big players. There are lots of hard problems resulting from bad connectivity that result in big $$ tech funneling traditional net uses onto their services, by investing engineering efforts (and complexity) into heroic engineering feats to work around the bad connectivity. The complexity means high barrier to entry to compete with them. Codecs yes but also clever distributed caching, cloud storage, UIs that predict what the user does next, video calls have to go through corporate encoding/multiplexing proxies instead of p2p, file sharing has to be of the hard "sync most likely needed needed files" variety with proprietary server side smarts, instead of just "mount remote share", etc.