You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 9, 2018. It is now read-only.
Thanks for every distributor, bring so great app,
Now, I expect a interesting using journey.
Thanks to everyone.
But why,
vim is hot, web is hot, js is hot, node is hot,
However,
why does vim.js developing is so cold?
I am so puzzled with this,
Would someone thinks like what I thought?
Would someone discusses on this issue?
The text was updated successfully, but these errors were encountered:
I post a issue before #37, and have strong interesting on watching this project.
As my view, I think maybe there are few resions cause that:
Maybe this project can not provided enough benefit for @coolwanglu , so he have no enough motivation to keep updating.
VIM is hot, and web is hot, but maybe VIM is hot on some people, and web is hot on another people, and the two kinds of crowd have very small intersection.
Less documentation and community supporting cause very few feeback @coolwanglu can get. And it make the author hardly keep passion on this project
It has only 1.6k stars, this repo got 4k stars. but look at the issue list, I got 1000+ issues, this repo just got less than 50 issues. For a opensource project, starts is not a strong feeback, issue it is.
Issue list is the key to make author keep going on.
Whatever, but I still think this is a very good repo, and maybe I will give my contribution in future. :)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Thanks for every distributor, bring so great app,
Now, I expect a interesting using journey.
Thanks to everyone.
But why,
vim is hot, web is hot, js is hot, node is hot,
However,
why does vim.js developing is so cold?
I am so puzzled with this,
Would someone thinks like what I thought?
Would someone discusses on this issue?
The text was updated successfully, but these errors were encountered: