VNC code forks...

[Lincoln A. Baxter]

One thing that I don't understand, especially now that original VNC 
authors are active again (RealVNC), is why to we have to have some many 
code forks:

    RealVNC
    TightVNC
    UltraVNC

and at least several more I cann't thing of off the top of my head.

Linux (the kernel anyway), has managed to maintain a common code base 
for more than 10 years now. Why cann't the various folks building VNC 
functionality, merge their efforts?  More bugs will be fixed and more 
features would be added in a shorter time frame by far, once the initial 
merge were completed, and a public CVS repository created (source forge 
comes to mind).

Lincoln