Skip to content

Please close this project for now. #53

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

Closed
jackey opened this issue May 31, 2018 · 7 comments
Closed

Please close this project for now. #53

jackey opened this issue May 31, 2018 · 7 comments

Comments

@jackey
Copy link

jackey commented May 31, 2018

You created node few years ago and it's very exciting project. we using and enjoy it. but it has a very big problem , we call "callback hell" or "callback shit". of course, some people create few solutions. but you didn't do anything to solve the problem and leaved node project.

Now, you back with deno, also it's basic on v8 engine. Will i like it ? no, i don't like it as i don't like you.

Before you created something that has relationship between javascript & v8 , please go to node project and fix the issues first. here you go

Before that, please close this project. Ok ?

Thanks.

@qti3e
Copy link
Member

qti3e commented May 31, 2018

@jackey Have you ever heard anything about async/await ???

@ry ry closed this as completed May 31, 2018
@jackey
Copy link
Author

jackey commented May 31, 2018

@qti3e
I tried many solution for async problem, none of them perfect. But as creator , he has more responsibility to find better solution from core v8 , not just npm package.

Do u know how many years of php author to maintained PHP ? Python ?
Ry just like a child that boring a toy and then change new one.

thanks.

@qti3e
Copy link
Member

qti3e commented May 31, 2018

@jackey Everyone is free to do whatever he/she wants to do in his/her life : )

By leaving Node, he just made a personal decision, you can't ask why...

@jackey
Copy link
Author

jackey commented May 31, 2018

@qti3e
As u said it's free to do whatever he wants. But we have a word "responsibility" . He doesn't have it .

@styfle
Copy link
Contributor

styfle commented May 31, 2018

@jackey Why do you no longer maintain markdown?

There are at least 10 people who starred it and you stopped working on it since 2015!

Do you have a responsibility to maintain it?

@jackey
Copy link
Author

jackey commented May 31, 2018

@styfle
It's totally difference from node. None of them to use it.

@kiddkai
Copy link

kiddkai commented May 31, 2018

@jackey please provide constructive feedbacks and make real contributions to the oss community.
And please, read the guidelines https://opensource.guide

@denoland denoland locked as too heated and limited conversation to collaborators May 31, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants