You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Loopback is a nice peace of technology, but searching for help is quite hard, because of lots of network stuff related results when searching for "loopback". Changing the name of your product on the next major release could help solving this (IMHO) big issue (for searching and gaining popularity). So, consider renaming loopback for search engine optimization. This would even help new developers to distinguish the new release (and it's breaking changes) from the various, abandoned advices on "loopback" in forums, etc.
Loopback is a nice peace of technology, but searching for help is quite
hard, because of lots of network stuff related results when searching for
"loopback". Changing the name of your product on the next major release
could help solving this (IMHO) big issue (for searching and gaining
popularity). So, consider renaming loopback for search engine optimization.
This would even help new developers to distinguish the new release (and
it's breaking changes) from the various, abandoned advices on "loopback" in
forums, etc.
—
Reply to this email directly or view it on GitHub #496.
@HansHammel good points, I was concerned about the affiliation to the network reference myself when we first named it. At this point we would have to weigh what we've optimized for loopback + nodejs versus something entirely different with a distinguished name. There's also some brand affiliation with the "loop" in LoopBack that was on purpose. I'll discuss with Issac to see what makes sense. In the meantim loopback + nodejs (or node) has been what we've optimized for.
I used "strongloop loopback", but searching for the a vendor name will (most probably) point you to their domain, or, in our case, the official API documentation of loopback, and that's not always helpful/ intended. So, just to make this clear, the idea was to give other, not directly related, resources (like e.g. stack overflow) a chance to be discovered via goolge, too. You know, people are not used to describe/ tag their posts with a vendor's name, but these community sites are good sources and vital for development, in a narrower and broader sense.
Update:
Just tried "node.js loopback datetime format", only the first result is a direct hit (surprise, surprise on strngloop.com) the rest is all about node.js. "strongloop loopback datetime format" gives better results (with the drawbacks mentioned). OK, this is a dump search, but it shows that optimizing for "node.js loopback" is rather impossible. There is so much node.js related stuff out there, that, in practice, the search has to hit on a single expression (the product name), only. And the specific topic, of cause...
Activity
offlinehacker commentedon Aug 25, 2014
+1
On Aug 25, 2014 8:26 AM, "HansHammel" notifications@github.com wrote:
nvdnkpr commentedon Aug 26, 2014
+1
altsang commentedon Aug 26, 2014
@HansHammel good points, I was concerned about the affiliation to the network reference myself when we first named it. At this point we would have to weigh what we've optimized for loopback + nodejs versus something entirely different with a distinguished name. There's also some brand affiliation with the "loop" in LoopBack that was on purpose. I'll discuss with Issac to see what makes sense. In the meantim loopback + nodejs (or node) has been what we've optimized for.
HansHammel commentedon Aug 27, 2014
I used "strongloop loopback", but searching for the a vendor name will (most probably) point you to their domain, or, in our case, the official API documentation of loopback, and that's not always helpful/ intended. So, just to make this clear, the idea was to give other, not directly related, resources (like e.g. stack overflow) a chance to be discovered via goolge, too. You know, people are not used to describe/ tag their posts with a vendor's name, but these community sites are good sources and vital for development, in a narrower and broader sense.
Update:
Just tried "node.js loopback datetime format", only the first result is a direct hit (surprise, surprise on strngloop.com) the rest is all about node.js. "strongloop loopback datetime format" gives better results (with the drawbacks mentioned). OK, this is a dump search, but it shows that optimizing for "node.js loopback" is rather impossible. There is so much node.js related stuff out there, that, in practice, the search has to hit on a single expression (the product name), only. And the specific topic, of cause...
superkhau commentedon Feb 26, 2015
@altsang Is this still relevant?
superkhau commentedon Feb 4, 2016
@chandadharap @bajtos Can I close this issue? It's been around for more than a year and I don't think it'll be resolved anytime soon.
superkhau commentedon Feb 4, 2016
Closing as per conversation with @chandadharap.