Show HN: Ng-classy – Use Angular 1 and ES6 with ease
1–10 of 20 posts
Re: Show HN: Ng-classy – Use Angular 1 and ES6 with ease
#2Hey, 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/
Re: Show HN: Ng-classy – Use Angular 1 and ES6 with ease
#3Hey, 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/
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.
Re: Show HN: Ng-classy – Use Angular 1 and ES6 with ease
#4Hey, 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/
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.
Re: Show HN: Ng-classy – Use Angular 1 and ES6 with ease
#5Earlier quoted context omitted.
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.
Careful with those assumptions, friend.
Re: Show HN: Ng-classy – Use Angular 1 and ES6 with ease
#6Decorators are an ES7 proposal -- they don't exist in ES6.
Re: Show HN: Ng-classy – Use Angular 1 and ES6 with ease
#7Decorators are an ES7 proposal -- they don't exist in ES6.
Good point, fixed https://github.com/eaze/ng-classy/commit/90ad4d8f493daad38f4...
Re: Show HN: Ng-classy – Use Angular 1 and ES6 with ease
#8Hey, 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/
Starting a new Open Source Project
[ ] 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
Re: Show HN: Ng-classy – Use Angular 1 and ES6 with ease
#9Re: Show HN: Ng-classy – Use Angular 1 and ES6 with ease
#10Hey, 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/
Starting a new Open Source Project [ ] 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
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.