4 ms·
Diverging from the topic slightly, I'm very concerned by the state of VNC today. A few years ago it was thriving and there were many open source clients and se
by axiolite 6y ago
Diverging from the topic slightly, I'm very concerned by the state of VNC today. A few years ago it was thriving and there were many open source clients and servers competing, with active communities.
RealVNC took over the lead of active development, and seemed to successfully undermine all the competing projects. But then RealVNC went closed source and nothing ever appeared to fill-in for them after.
UltraVNC seems to be the only healthy VNC community, but it is sadly a Windows-only project, with their own extensions which don't appear in ANY other client (except for ssvnc, which is now dead). This means non-Windows clients don't get the benefits of UltraVNC developments, and may not work at all (e.g. the one-click UltraVNC package won't work with any other vnc viewers).
TightVNC is still limping along, but now as a Windows-only.
TigherVNC is alive, but only just doing the basic maintenance needed, and lagging behind at that. Doesn't look like non-essential but highly useful features will ever get worked on there.
VNC servers are increasingly having show-stopping problems with modern Linux desktop environments. Projects like GNOME keep using more GPU hardware-acceleration where no fallback exists and no workaround is available for vncserver/Xvnc even quite some time after.
It seems a dire state of affairs. We're losing the standard, open source, platform independent and interoperable remote display protocol we all took for granted for the past several decades, and nothing on the horizon looks like any improvement to this state of affairs will be forthcoming. Those projects still active are fracturing off with proprietary changes limiting or even preventing interoperability. Am I missing something?