NX

NoMachine is an alternative remote desktop solution reminiscent of LBX that has made significant inroads in several quarters, and that everyone suggests when I mention or in one of my posts.

So, for the record, here’s my take on it:

  • The client (version 1.5 and previous) is one of the absolute worst applications I have ever had the displeasure of running. I will freely grant that 2.0 has improved, even if it does not feel particularly Mac-like.
  • Even prior to neatx, the server was a needless hassle to install and manage anywhere (even after FreeNX appeared), and mucks about entirely too much with . I can apt-get or yum on any box and get it working in a couple of minutes. And yes, I am aware of the freenx package in Core 5 extras, and of the peculiar need to nxserver --adduser and nxserver --passwd whomever feels like using NX.
  • The client is mostly the same: I can fire up a 260KB executable from a pen drive (or use the built-in client) in any machine on the planet, and it’s nearly as easy to get vncviewer, rdesktop or a binary on other machines. Or, god forbid, just use plain old forwarding…
  • It has (for me) no significant advantages over or (and by VNC I mean optimized VNC protocols) atop .

I especially like returning to a VNC workspace and finding it just as it was before I disconnected, and routinely use both VNC and RDP over UMTS links without any performance issues. Even if NX now has support for persistent sessions, I find it an unnecessary hassle.

My only real gripe with VNC is that current Mac OS X clients have very serious keyboard mapping issues that make it damn near impossible to code or do system administration tasks using a Portuguese keyboard.

Otherwise, I’ll take it over NX any day.