Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Developed Neo-async, an improved version of async #709

Closed
suguru03 opened this issue Feb 2, 2015 · 7 comments
Closed

Developed Neo-async, an improved version of async #709

suguru03 opened this issue Feb 2, 2015 · 7 comments

Comments

@suguru03
Copy link
Contributor

suguru03 commented Feb 2, 2015

Hi. I have developed Neo-async, basically it is an improved version of the original async module. It keeps all the original functions, so it is thought to be a drop-in replacement. At the moment it only includes just a small extra functionality. Neo-async offers better overall performance and almost 100% code coverage.

We are using Async for managing asynchronous operations in our project since it offers a straightforward solution and has the source code well organized. We use it very often in our code, but we have detected some perfomance problems, this is our motivation to create a version with these perfomance problems solved.

I would really appreciate your feedback or any comments. Thank you.

@thammin
Copy link

thammin commented Feb 5, 2015

Impressive! 👍

@martinheidegger
Copy link

If it truly is a "drop-in-replacement" then I wonder why you not just created a PR here to improve the quality of async? I assume that there are some "incompatibilities". Would love to know what they are about.

@suguru03
Copy link
Contributor Author

suguru03 commented Feb 5, 2015

@thammin @martinheidegger
Thanks for replies!
I have been using Async in production, and an error occured due to a bug. I sent a PR at that time but it has not been merged yet. That is my main motivation to develop Neo-Async as a separate project. In order to achieve a better performance Neo-Async has been built from scratch. The code structure of Neo-Async is far from Async now, so it could not be merged anymore.
I think the relation between async and Neo-Async could be similar to the one between Underscore and lodash. I am also planning to implement more methods to improve the usability.

@ralgara
Copy link

ralgara commented Mar 11, 2015

@suguru03

Great job on Neo-Async. Also here trying to find a fix for #508/#512 -- there is a similarly pending PR. Any chance it can be addressed in Neo-Async?

@suguru03
Copy link
Contributor Author

@ralgara

Thank you for your comment.
OK, I try to fix it ASAP.

@aearly
Copy link
Collaborator

aearly commented May 19, 2015

BTW, since we have a couple more maintainers now, PRs will start getting merged again. 😄

@suguru03
Copy link
Contributor Author

Thank your very much for your contribution.
I’m very happy for published new version and want to improve async :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants