Hacker News Reader

Comment by Sephr | Hacker News Reader

One way to escape callback hell is to use a async.js (https://github.com/eligrey/async.js), which uses yield to abstract away callbacks. It's Firefox-only (JS 1.7+) though, but that can probably be resolved by using a JS parser and replacing every yield with JS 1.5 callbacks.

Full disclosure: I wrote async.js.

View on HN

There's also this library: https://github.com/caolan/async

That library uses callbacks and isn't really related other than the name. I don't think that the author googled async.js to see if the library name was already taken.

I think it's more likely he found it was not taken on npm so he took it. Async is, these days, one of the most popular libs on npm.

https://github.com/caolan/async: 3293 stars on Github

https://github.com/eligrey/async.js: 15 stars on Github

Sorry, you lost this one.

Sorry, but what do stars have to do with it? That's like saying DuckDuckGo should be allowed to rename itself as Google if they become more popular than Google. https://github.com/caolan/async had zero stars (i.e. didn't exist) back when I released async.js.

I'm just saying you're going to have a hard time convincing everyone that your project is the "async" JavaScript library. I presume you don't plan on suing them for trademark infringement.

It's annoying (it's happened to me too) but I don't think there's much you can do about it. Especially when the name is incredibly generic.

Reply on news.ycombinator.com