[shrig94]

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.

[nateabele]

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.

[simi_]

Sorry, but this is hardly rocket science: https://www.google.com/search?q=ng+classy

[atjoslin]

I didn't check the web-at-large, that's why. I just thought 'classy! It's classes.' Then I checked npm. Then I pushed it.

Probably was a bad idea.