8 ms·
I would pick a different name. The dependency manager everyone in PHP uses has the same name: https://getcomposer.org/ https://getcomposer.org/ It will be a pa
by jafaku 12y ago
I would pick a different name. The dependency manager everyone in PHP uses has the same name: https://getcomposer.org/ https://getcomposer.org/
It will be a pain to google anything about your project. Take a look at stackoverflow: https://stackoverflow.com/search?q=composer https://stackoverflow.com/search?q=composer
- orthecreedence 12y agoYou may be right, but the projects both started around the same time (mid-late 2011) and I think two projects in different languages that do separate things sharing the same base name isn't a big deal, at least not as bad as having a language called "go" ...which seems to do just fine anyway =].
- MAGZine 12y agonobody is stopping you from using it, i think the argument being made isn't that "they had it first," but that a lot of materials are going to conflict with the already-established PHP Composer, and that it presents a possible confusion for your (potential) users. I'd rename it if it were my project. And "go" is pretty bad, but it's clear that if you're looking for specific resources, 'golang' is the appropriate tag/search term.
- theOnliest 12y agoAt the very least, I'd change the <title> of the home page to remove some ambiguity. Right now it says "Get Composer | Composer.js", and the URL for the PHP composer is getcomposer.org.
- orthecreedence 12y agoNot a bad idea, I'm fine with this change.