Except the same argument with regard to J2EE and JDEE can be made about
EJB and EJE.  All and all, I think that EmacsJDE would be the best
choice (assuming it wouldn't be objected to by JD Edwards).  Here's why:

1. It would allow searched for JDE to potentially turn up EmacsJDE as
well (especially when searching for JDE and JAVA).
2. It incorporates the name of a FSF product, which might give it some
implicit trademark protection, although I still think trademarking might
not be a bad idea.  Does anyone know what if any trademarks they own?
3. It makes it clear that it is tightly coupled to emacs, which is
potentially a double edged sword with regard to attracting interest, but
is true none the less.
4. The emacsjde.org, .com, .net, are all currently available (so is
jdee.org, but jdee.com is taken right now)

The only thing I don't like about it is that it's slightly verbose.
However, I would not be surprised if developers still referred to it as
JDE within programming circles (hence my questioning of whether JD
Edwards would be ok with this).


Alan Hadsell wrote:

> I vote for EJE (Emacs Java Environment).  Easy to remember, can't be
> confused with JDE.  The current claimants for this acronym are:
>
>    European Journal of Endocrinology
>    The Elgin, Joliet and Eastern Railway
>    The EJE Group (Environmental Design and Planning,
>         Newcastle NSW, Australia) http://www.eje.com.au
>    Errington John Enterprises Ltd.
>
> And I DON'T think that harassing JDEdwards about it is going to do
> any good.  They do have the domain name jde.com, and they've had it
> since 1998 (although jdedwards.com seems to be their main domain
> name).
>
> Let's just change the name and get on with our lives.  Don't we have
> better things to do?
>
> --
> Alan Hadsell
> "Whatever does not kill me makes me stranger".




--
****************************************************
Jim LoVerde, Sr. Technical Architect
nVISIA, http://www.nvisia.com
voice:  312-985-8178   pager: 800-862-0399 #17086723
fax:    312-985-8101   epage: [EMAIL PROTECTED]

S/MIME Cryptographic Signature

Reply via email to