Re:Composer.js: a framework for building complex single-page...
by theOnliest on Sunday January 25, 2015 @05:29PM
(#8944510)
At 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.
Re:Composer.js: a framework for building complex single-page...
by orthecreedence on Sunday January 25, 2015 @05:33PM
(#8944520)
Not a bad idea, I'm fine with this change.
Re:Composer.js: a framework for building complex single-page...
by orthecreedence on Sunday January 25, 2015 @05:11PM
(#8944458)
You 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 =].
Re:Composer.js: a framework for building complex single-page...
by MAGZine on Sunday January 25, 2015 @06:05PM
(#8944626)
nobody 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.
It will be a pain to google anything about your project. Take a look at stackoverflow: https://stackoverflow.com/search?q=composer