[X2go-dev] getting features inside neatx/freenx instead of developing something different

John A. Sullivan III jsullivan at opensourcedevel.com
Wed Jun 30 21:49:45 CEST 2010

On Wed, 2010-06-30 at 18:58 +0000, Eli K. wrote:
> Hello x2go list,
> I've added one of my not so important mail accounts to this list to share my opinion about nx based development in the future. I don't like mailing lists because they only collect spam (to add my opinion to a already discussed topic).
> I've read some of the mesages here and I've taken a look to this project. I really don't think this is a good idea to work on a not compatible nx server. There are already enough free servers and clients in the world and we all should try to save a amount of compatibility to all projects.
> There is also a plugin for mozilla (moznx) so you won't need to develop a own. 
> Although i like the idea of the file transport and print module of x2go (pulseaudio too is already possible with opennx).
> If you would change to python, i would help you to get things to work with neatx/freenx. Then you too would have no problem with the packaging, because everything you need is already done.
> What do you think about at minimum getting those interesting features build up in external programms, so you can use it with all nx servers (or even vncs)?
I can't speak for the developers but I think the goal is to develop
something broader than any of the NX projects.  I suppose it's a bit
like I've taken great open source projects like iptables, iproute2,
openswan, and openvpn and built a new project for a powerful network
security framework in the ISCS project (iscs.sourceforge.net).  So Heinz
and Oleksandr have taken the NX libraries, pulseaudio, sshfs, openldap,
etc., and combined them into a broader project.

We had originally planned to use NoMachine for our new company but were
frustrated with the sound problems.  We thought about starting a new
project to combine technologies including NX to do what we needed to do
but that's when we stumbled across X2Go.  We haven't looked back.

I think the lack of compatibility is not about isolationism but simply
because the goals of the project are bigger than simply an NX
client/server.  At least that's my take - John

More information about the x2go-dev mailing list