Re:KasmVNC – WASM Based VNC Server and Client
by mysterydip on Saturday March 30, 2024 @07:43AM
(#39873913)
> While VNC is in the name, KasmVNC differs from other VNC variants such as TigerVNC, RealVNC, and TurboVNC. KasmVNC has broken from the RFB specification which defines VNC, in order to support modern technologies and increase security.
I understand the reason why you'd want to break away from the spec, but why call it VNC then?
Re:KasmVNC – WASM Based VNC Server and Client
by Gys on Saturday March 30, 2024 @08:33AM
(#39874227)
While I agree using 'VNC' is a little questionable, I do think their use case together with graphical docker containers is rather cool: https://github.com/kasmtech/workspaces-images
Re:KasmVNC – WASM Based VNC Server and Client
by SubiculumCode on Saturday March 30, 2024 @10:19AM
(#39875135)
By which I succinctly implied: does it support modern compositors (not just X), so that it can be used with most recent desktops. It IS perhaps the most important question in the space right now. VNC works with X only.
Re:KasmVNC – WASM Based VNC Server and Client
by ndsipa_pomu on Saturday March 30, 2024 @09:56AM
(#39874933)
I've been trying this out on a bunch of different servers and I find it to be quicker and more convenient than ordinary VNC. However, I couldn't find a version to put on OEL/Redhat 7 which is annoying.
Re:KasmVNC – WASM Based VNC Server and Client
by anon291 on Saturday March 30, 2024 @10:00AM
(#39874963)
At this point there are three competing 'cross-platform' VM technologies (Java, WASM, and .NET - the latter of which is an ISO standard). What is the point?
I understand the reason why you'd want to break away from the spec, but why call it VNC then?
[1] https://en.wikipedia.org/wiki/Remote_desktop_software
[2] https://en.wikipedia.org/wiki/Comparison_of_remote_desktop_s...
[3] https://en.wikipedia.org/wiki/Desktop_virtualization#Remote_...
Just curiously, what's the name "Kasm" come from?
see also https://news.ycombinator.com/item?id=39874356