Hey, I have a reasonably popular project with a very similar name. It's not a huge issue but it might be a bit confusing for people using our projects: http://davej.github.io/angular-classy/
[ ] 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
I'd agree that this namespace conflict is by no means ideal.
It's hard for someone to scope out the world of similarly-named packages in npm, determine which ones are actually used, and then name their package--even after investing in this process, it can be easy for one to miss something similar. That's probably why this happens so often.
People are being overly critical of atjoslin, given that he admitted in his edit that his intentions were not foul.
I know the internet is a place where tone doesn't really come across, but I'm just poking a little fun, not trying to be critical, since I'm not really invested one way or the other. In fact, if anything, it behooves me as an active participant in the Angular community not to pick fights & make enemies (hi, atjoslin!). :-)
> 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.
Unfortunately, this is going to happen. Best wishes with your project.
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.
The tone of this response as well as the tone of the README in the actual project ensure that I'll pass on this, as I can bet on receiving dismissive and snarky responses to any issues/pull requests.
What in the world is that @ symbol doing? I've never seen that in ES6. It makes this thing look horrid and nonidiomatic, unless I'm just ignorant, which I could be, and both could be true.
That is a TypeScript decorator[0]. It's not a Real JavaScript Thing™ in the TC-39 sense, but you can use it if you're willing to put up with more build tools.