[ ] 1. Choose a nominally unique name within language/package space
[ ] 2. Okay, at least choose a unique name within the comparatively small sub-community you're targeting, so as not to invite unnecessary confusion for literally everyone involved
[x] 3. Post on Hacker News
People are being overly critical of atjoslin, given that he admitted in his edit that his intentions were not foul.
> That's probably why this happens so often.
So often?
> People are being overly critical of atjoslin, given that he admitted in his edit that his intentions were not foul.
Well, maybe not-foul intentions are a high enough bar, but I think good intentions might look something like taking the extra half-hour (as an author/maintainer of numerous OS projects, I know it doesn't take that long) to find a slightly less-similar name. As this is a new project, I can't imagine the impact on your (checks GitHub, sees 31 stars & 4 watchers) community will be all that substantial.
Again, I have no particular investment here (okay, okay, technically I have 2 HN comments-worth of investment, so that adds up to... wait, yup, basically nothing). This is just a little friendly advice, and worth what you paid for it.
Edit: I'm only trying to be straightforward. I meant only what I said: name collisions do happen, especially in the cluttered npm namespace, and will continue to happen.
And I meant what I said in that I do wish your project the best. No foul intent.
[0] http://blogs.msdn.com/b/typescript/archive/2015/04/30/announ...
