KasmVNC – WASM Based VNC Server and Client | Hacker News Reader

KasmVNC – WASM Based VNC Server and Client

github.com

36 pointsMrBuddyCasino13 comments

> 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?

Dishonesty and willingness to piggyback an already established industry/market.

Do you know a different term that conveys the same idea and is similarly short?

Remote Desktop {Tool,Technology}: RDT

The Kasm docker containers are very cool. It's all on GitHub, too.

Just curiously, what's the name "Kasm" come from?

Remote Desktop Software [1] [2] or Virtual Desktop Infrastructure [3]. Rfb is the protocol used by VNC, btw.

[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_...

Yeah that’s equally short.

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

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.

Wayland?

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.

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?

Another RMM to block for security <3

Reply on news.ycombinator.com