Closed tj closed 11 years ago
Thanks for the gentle hint. Indeed, it isn't a big deal because a generic IT term like "component" obviously always creates some name conflicts. But our projects play different games anyway: your "components" are actually installation-time items (usually aka packages) for JavaScript while my "components" are run-time items on the software architecture level. I actually named my project ComponentJS because it supports the "Component-Oriented Programming" architecture paradigm in JavaScript. Some history of my project you find under http://componentjs.com/imprint.html
So, beside the common JavaScript language context our projects do not overlap in scope at all. And it makes sense for both projects to carry the term "component" in their name, of course. A user even can use both at the same time: install my run-time library with the help of your packaging environment. Voila!
Keep up your good work and valuable contribution to the steadily growing world of Open Source Software...
hey man! Not a huge deal but I just wanted to point out https://github.com/component/component in case you haven't seen that effort, we've got over 600 components so far in the last ~4 months or so