Do you guys have any plans on changing the name of LLBLGen Pro? The reason I ask is, the name does not roll off the tongue very well here in the States....

We've been evaluating a few different frameworks and since LLBLGen Pro is hard to say in conversation...my director has decided to refer to it as "LL Cool J". While it is humorous, and in no way takes away from the product - in other environments, the current name may is not as marketable as some of the other single-word-named frameworks out there.

Just a thought...I'm probably nit-picking....it's Monday morning =)

-G

GiorgioG wrote:

Do you guys have any plans on changing the name of LLBLGen Pro? The reason I ask is, the name does not roll off the tongue very well here in the States....

We've been evaluating a few different frameworks and since LLBLGen Pro is hard to say in conversation...my director has decided to refer to it as "LL Cool J". While it is humorous, and in no way takes away from the product - in other environments, the current name may is not as marketable as some of the other single-word-named frameworks out there.

You're not the first mentioning this to us, nor the first calling it LLCoolJ or LLCoolGen hehe . We know it's a name which is hard to pronounce, and if we would have do it all over again, we'd pick a different name perhaps. However, the first LLBLGen tool (without 'pro') was a code generator for classes and procs (http://www.sd.nl/software) and it was a big success. When we were working on the successor, LLBLGen Pro, we used the name of the first generator, because it was so widely known and the pro version is the successor of it after all. If we would have picked a different name, it might not have been a big success.

I admit, I picked the initial name for the free toolkit, not thinking about the consequences later on in future versions, as I didn't expect it to be such a success . Needless to say, I'm not allowed to pick names again for tools we release