Earlier quoted context omitted.
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 ed…
Show HN: Ng-classy – Use Angular 1 and ES6 with ease
11–20 of 20 posts
Re: Show HN: Ng-classy – Use Angular 1 and ES6 with ease
#12Earlier quoted context omitted.
Careful with those assumptions, friend.
[deleted]
Re: Show HN: Ng-classy – Use Angular 1 and ES6 with ease
#13Decorators are an ES7 proposal -- they don't exist in ES6.
Re: Show HN: Ng-classy – Use Angular 1 and ES6 with ease
#14Earlier quoted context omitted.
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 ed…
Sorry, but this is hardly rocket science: https://www.google.com/search?q=ng+classy
Probably was a bad idea.
Re: Show HN: Ng-classy – Use Angular 1 and ES6 with ease
#15Re: Show HN: Ng-classy – Use Angular 1 and ES6 with ease
#16Earlier quoted context omitted.
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 ed…
> 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.
Re: Show HN: Ng-classy – Use Angular 1 and ES6 with ease
#17What 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.
[0] http://blogs.msdn.com/b/typescript/archive/2015/04/30/announ...
Re: Show HN: Ng-classy – Use Angular 1 and ES6 with ease
#18What 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. [0] http://blogs.msdn.com/b/typescript/archive/2015/04/30/announ...
Re: Show HN: Ng-classy – Use Angular 1 and ES6 with ease
#19Earlier quoted context omitted.
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. [0] http://blogs.msdn.com/b/typescript/archive/2015/04/30/announ...
That's also a Javascript decorator. You can use it with Babel today if you pass in `{stage: 0}`. https://github.com/wycats/javascript-decorators http://babeljs.io/docs/usage/experimental/
Re: Show HN: Ng-classy – Use Angular 1 and ES6 with ease
#20What 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. [0] http://blogs.msdn.com/b/typescript/archive/2015/04/30/announ...