Can we rename this project?

[jamesmenera]

I am honestly not trolling and use this library everyday. But It is becoming harder to find any useful information while searching the internet using the terms "ember-model", "ember-model.js" or "ember model". The search results are now saturated with the words "ember", "model" and "js". Most of what comes up is "ember-data", "DS.Model" and the Ember.js Model Guides and Docs.

It is becoming increasingly more difficult to find answers pertaining to "ember-model.js" the library on stack overflow, blogs and other resources. I suggest that we change it to a more unique name.

Here's just one example:

Does anyone else have any feedback?

[cigoe]

+1 on this, I have been using the library for several months now and have noticed the results returning more ember core/cli/unrelated related results as the screenshot above shows

[givanse]

The problem to solve is not the name of the project, this will keep happening always.

Add tools to your research toolbelt, search examples:

"ember-model.js"
site:stackoverflow.com "ember-model"
"unit test OR relationships" "ember-model"

Also, many of the projects that Ember has given birth to are very recent, there won't me that many results.

[jamesmenera]

@givanse While what I am asking is a bit extreme and I realize this, I think that we should not be tied down by a couple of words. Honestly, changing the name has no impact on the code inside the library, but betters the overall experience to those using it.

We gain nothing by keeping the same name except some confusion and hiding helpful resources. But we would all benefit from it being more unique. Every page that even remotely mentions ember.js has the words "ember" and "model" in them, clouding the pages that have actual useful information that would be beneficial to the ember.js and ember-model stack.

I think with that being said, I have a hard time believing that it would be easier to tell somebody to change their searching habits than to tell them to search for "ember-sleepy-model" or "ember-fashion-model". ;)

I am sure we can all agree that our end goal is putting ember.js in the hands of more developers, making them more productive and lowering the barrier to entry rather than holding onto a name that prevents developers from finding useful information quicker.

After all, aren't we all just writing a variant of sproutcore 2.0? See what I mean?

[scottmessinger]

I can't agree more with @jamesmenera's comment "We gain nothing by keeping the same name except some confusion and hiding helpful resources. But we would all benefit from it being more unique."

I'm confused by @givanse's comment, "The problem to solve is not the name of the project, this will keep happening always." If the confusion is caused by a non-distinct name, changing the name to a distinct name will prevent this from happening. @givanse: could you elaborate?

[grapho]

Based on my experience in learning EM, i think the problem with not finding much about ember-model is the fact that there is not much ember-model content out there. I can probably count on my hand how many actual tutorial style information I have found. Stackoverflow has the best info I have found so far, but it the subject matter is pretty focused on particular cases... difficult to gain a full comprehension....

To address the question specifically... changing the name will NOT improve search results, in fact will probably make it worse...