7 ms·
Very much this. Running the X11 protocol over the network is usually not a good idea anymore. By the way, does anyone know of a VNC-like solution that can use
by amelius 4y ago
Very much this. Running the X11 protocol over the network is usually not a good idea anymore.
By the way, does anyone know of a VNC-like solution that can use MPEG compression?
Also, VNC could be better if it could increase the quality of parts of the screen once they stop updating. E.g. in TigerVNC setting a low bitrate doesn't improve the quality of text once the text stops changing.
- chpatrick 4y agohttps://xpra.org/ https://xpra.org/
- aidenn0 4y agoNomachine's server and client are closed-source but work great. For open-source solution for quickly remoting into an existing display, I use freerdp-shadow-cli which is way more stable than x11vnc and uses the RDP protocol instead.
- RealStickman_ 4y agoNomachine used to be open source. X2Go is the open source continuation of that.
- aidenn0 4y agoI think their current version is unrelated to what is now x2go
- msla 4y ago> Running the X11 protocol over the network is usually not a good idea anymore. It works well, though, and I'm not really interested in hearing that my own experience with it working well is a lie or some trick. Wayland gives up some things, and pretending that those things have no value isn't going to convince those of us who know they do. Also, those of us who use non-mainstream window managers (such as Window Maker) are not interested in hearing that we should switch to some UI which doesn't support our workflow just because it's more fashionable these days. There's a debate to be had here, and it needs to be had on the basis of facts, not lies.
- gbin 4y agoTBH This response is way too aggressive for the original comment. The facts stated are simply that today it is more efficient to encode video for remote graphical sessions because the X11 applications already changed a long long time ago to adapt to the modern world of GPUs and accelerated compositing. BW, latency, efficiency, everything became better because a super computer with thousands of cores can do that and lighten the load on the CPUs. It doesn't say it doesn't work... It doesn't prevent you neither from running X11 or even booting up a PDP-11 if this is your favorite workflow!
- d110af5ccf 4y agoThe problem is that the Wayland fans have a tendency (at least I feel) to significantly misrepresent things in their favor. Statements like "oh that's actually more efficient on Wayland". No, Wayland is incapable of the sorts of optimizations X can do by design. It is only more efficient if the X app is doing things in a specific way that doesn't take advantage of huge parts of the X protocol. Granted, most modern apps do exactly that at this point. That doesn't make such statements any less of a misrepresentation though. A much more reasonable claim would be that the network transparency afforded by the X protocol adds significant complexity which is no longer utilized by the majority of mainstream apps today. As such there's a reasonable case for dropping all that complexity from the core system and leaving it to peripheral libraries to handle on a case by case basis for the apps that want to make use of it. And the idea of lossy compression while using an image editing program being a desirable thing (as suggested elsewhere in this comment chain) is laughable. It's already bad enough reading text that's gone through lossy compression. I would never want compression artifacts while manipulating an image. My impression of Wayland so far is that I like the technicals but absolutely detest the people I encounter pushing it as a solution (it's quite similar to Rust in that regard I suppose). They would probably meet less resistance if they took more care not to misrepresent the overall state of things. I'll leave the link to KDE Wayland "showstoppers" for reference. Certainly that list is far shorter today than it used to be and many (not all) of the items are now solely on KDE's end. Nonetheless, fanboys have been claiming that Wayland is "production ready" the entire time. https://community.kde.org/Plasma/Wayland_Showstoppers https://community.kde.org/Plasma/Wayland_Showstoppers I'll switch to Wayland once it "just works" out of the box in terms of app integration on stable distributions including things like screen capture, fractional scaling factors, color management, all the stuff that works on X.
- satya71 4y agoI think TurboVNC had some extensions in that direction. But it’s been a while since I looked at it.
- aappleby 4y agoParsec, I think?
- POPOSYS 4y agoX2GO is the way to go!
- torginus 4y agoIf you're not afraid of big brother, I can recommend Chrome Remote desktop. You just install a server on the shared machine, and you can access your stuff using a regular browser thanks to the wonders of WebRTC.
- j1elo 4y agoI recently had to uninstall Chrome Remote Desktop, because it was breaking my (Ubuntu) system's ability to handle some basic permissions, such as mounting USB disks. It turns out that CRD is well known for breaking other seemingly random things, such as accessing your printer: https://askubuntu.com/questions/1196248/automount-when-clicking-on-disks-in-gui-file-manager-suddenly-stopped-working-in https://askubuntu.com/questions/1196248/automount-when-click...
- baq 4y ago> By the way, does anyone know of a VNC-like solution that can use MPEG compression? try this: https://xpra.org/ https://xpra.org/
- izacus 4y agoXPRA uses H.264, PNG or JPEG compression. Chrome Remote Desktop will use VP9 these days.
- stuaxo 4y agoNot sure on the exact compression but I'm sure Nomachine/NX must use some video compressing n, I'm even able to watch video over it without it dying.
- mark254 4y ago> By the way, does anyone know of a VNC-like solution that can use MPEG compression? You want xpra.
- LtWorf 4y agobut doing ssh -X is scertainly easier than setting up vnc.