2008/5/31 Duncan McGreggor
On Fri, May 30, 2008 at 2:03 PM,
wrote: On 03:31 pm, phil@bubblehouse.org wrote:
I have to say, personally, there's pretty much no way I would ever name a project 'Twisty' anything ;-).
OK, OK, I get it. Everybody hates "Twisty" :).
Seriously. I groaned audibly upon hearing about it :-)
I should have been more careful to separate the specific suggestion of "Twisty" (which was just something that popped into my head) in my original message from the need for a word like this. I wasn't totally set on it.
Of course, I understand this wouldn't be a requirement, but if this is to be a useful marketing technique, whatever the prefix is needs to be obvious, but also inconsequential. That's the thing that's great about the Java convention, once you're familiar with it, you pretty much stop seeing the J. Same with the tired but successful iSomething.
You've convinced me. I still think "Twi" sounds okay (better than "Twisty") "Tx" (evocative of "TwistedmatriX", "Transmit", "Twisted multipleXed"?) "T"? I'd suggest "Tw" but I feel like it has to be pronounceable, and "Tw" forces the first letter of your project to be a vowel (whereas "Tx" could be pronounced "Tix").
I think a one- or two-letter prefix is pretty much the best option
Man, I think you totally hit it on the nose with your "tx" suggestion: tx.snmp, tx.storage. I maintain the Twisted-JSONRPC package, and I will change the namespace from twisted.web.jsonrpc to tx.jsonrpc. Not only does it have a cool sound, entails "TwistedmatriX", is associated with "transmit", but it could also stand for "Twisted eXtensions" (in the "add on" sense). I really like tx. too and you perfectly explained why :)
jkk