[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-scripting-dev] eScriptMonkey naming

I really like “ScriptMyEclipse” , it addresses all the criteria that I’ve mentioned in my previous E-Mail.

 

What about shortening it to just “ScriptEclipse” and package names org.eclipse.scripteclipse.*

 

Thanks,

Martin

--

Martin Oberhuber, SMTS / Product Architect – Development Tools, Wind River

direct +43.662.457915.85  fax +43.662.457915.6

 

From: eclipse-scripting-dev-bounces@xxxxxxxxxxx [mailto:eclipse-scripting-dev-bounces@xxxxxxxxxxx] On Behalf Of Mickael Istria
Sent: Wednesday, September 11, 2013 10:40 AM
To: eclipse-scripting-dev@xxxxxxxxxxx
Subject: Re: [eclipse-scripting-dev] eScriptMonkey naming

 

Although I'm not a contributor, I'd like to give my 2 cents.

* IMHO, acronyms are generally very bad at getting attention and understanding from people out of the community. EASE and DSEE don't mean much to anyone, it's impossible to guess what the project is about from this acronym, I've not tried Googling it but I'm pretty sure that those acronyms are already used in some other contexts (just like any acronym), and it is easy to mess up and switch letters without paying attention. Also "ease" is a very common word, so it will make googling very difficult.
* What is the issue with long packages name? Almost no-one ever types it as it is often generated.

EScriptMonkey is not that bad but suffers from the competition of the hundreds of other EScript projects existing.
I would go for something more explicit, such as ScriptMyEclipse, with the long scriptmyeclipse package name; it costs a few extra characters but it's explicit, easy to remember, not competing with other names, and you can even make typos in your Google researches it will find it.

Cheers,

--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets