Should we continue using the term "NX"?

[mikedep333]

If you look at debian/control, you will see package descriptions like:

Package: libxcompshad3
...
Description: nx-X11 shadowing library
NX is a software suite which implements very efficient
compression of the X11 protocol. This increases performance when
using X applications over a network, especially a slow one.
.
This package provides a library for shadow session support.

Should we continue using the term "NX"? Or should we switch all references to "nx-libs"? Or perhaps replace both NX and nx-libs entirely with some other name like "LBX2"?

[mikedep333]

@gznget @sunweaver @nitomartinez @Ionic

I propose Xccc:

X11 Cached, Compressed and short-Circuited

Here is a proposed site design:
http://mikedep333.github.io/Xccc/
And the code for it:
https://github.com/mikedep333/Xccc

I believe that we need to rename nx-libs quickly (but not necessarily on the 3.5.0.x branch.)
Further reasoning is in the proposed site design.

[sunweaver]

How about Xc3? (Not that CCC is Chaos Computer Club in Germany/Europe, so there is a slight name clashing...).

[mikedep333]

I was wondering that myself. I thought that "CCC" sounded familiar.

Some other piece of software is already called "XCC". But by using "Xc3", we can put the project name in the binary names (Xc3proxy and Xc3agent).

[Ionic]

I don't think a digit in the name is a great idea. Can easily be confused with a version number or other stuff.

I'd rather look for something like "NAX" (Network Accelerated X) or the like.

[mikedep333]

I tend to agree with @Ionic . It can also create confusion with "X11" or "X2Go", but nx-libs is not specific to X2Go.

I still think Xccc is best because it highlights the 3 things that nx-libs does, but VNC only does 1 of (compression.) But my 2nd favorite so far is NAX.

If only the acronym "WAX" (WAN Accelerated X) didn't have a bad connotation (Wax is sticky, which means it is not fast moving. Also, "ear wax.").

[Ionic]

X11 actually is called X11 because it's the 11th protocol version. :)
(Although admittedly nowadays it's its own trademark.)

X2Go is "kind of okay" due to the the digit being surrounded by other letters.

WAX... there was also VAX, so...

I'm trying to come up with something involving "X", "accelerated" or "enhanced" and "network" (or similar), but haven't had a brilliant idea yet. Network enhanced X Technology? Better not. ;)

[mikedep333]

@Ionic, yeah.

I am going to look through dictionary files for either a name or inspiration. Not that I have given up on Xccc, but there may be a better name.

Also, do not forget this lesson on naming software (or games):
The word Narbacular, which does not exist in any dictionary, was chosen primarily to aid in internet search engine results.

[sunweaver]

@mikedep333: Let's make sure that the new name is easily pronouncable and gives a fine melody when saying it. Xccc is a little tongue twister. Do we necessarily need to stay below 8 chars for the executables?

How about these, may: Xccc (nxagent), x3cproxy?

[sunweaver]

actually, xc3proxy...

[mikedep333]

Hi @sunweaver,

It is true that Xccc is a bit long to say. However, I liked Xccc because it highlights the 3 things we do (Caching, Compression and short-Circuiting.) And "short-Circuting" (a term I made up for what we currently do to eliminate round-trips) is also a fine excuse for the executable having "Xcc" in the name.

Like I said, I intend to look through the dictionary files for more inspiration. I am open to other suggestions, including other names, and including adopting 1 name but having different names for the executables (like you suggested.) The terms "agent" and "proxy" are themselves confusing.

Even if we do adopt a different name, it may be a good idea to use the slogan "X11 Cached, Compressed and short-Circuited".