This question came up just a few days ago https://groups.google.com/d/topic/nodejs/u-uhaXderi8/discussion
Eldar had mentioned nipster <http://eirikb.github.com/nipster> which is an interesting approach which combines github watchers, forks, and npm stars for ranking, which seems like a good start for a community driven ranking. On Friday, 13 April 2012 09:01:17 UTC-5, Tito wrote: > > Eldar, > > So newbies should dig code on GitHub? Seriously? With all due respect, > what you're saying is nonsense. I have no idea how many modules exist on > GitHub, but at the time of this writing, npm contains 8839 packages. Dig > around and study them? It's awesome you have all this time to play with, > but most of us do not. I do that once I have zeroed-in on a particular > solution, sure. But what if you don't know where to start? It's been said > over and over that one of the main problems developing with Node if the > lack of thorough information about all these packages. Yes, there are great > resources out there, but oftentimes they're biased, old, skewed, incomplete > or simply… wrong. Having a single place where developers can pitch and > evaluate, comment and compare different modules would be awesome. Soon > enough, it would be fairly obvious where the pros are spending time. > Newbies would not feel intimidated knowing where the good stuff lies. > > Perhaps you're an expert and don't need it. If that's the case, great. But > for the rest of the developers joining Node's community and to the ones > that are not so new, this place would be *wonderful*. > > -- Tito > > On Apr 13, 2012, at 9:46 AM, Eldar wrote: > > there is no real place/tool to help achieve this overlook (apart from some >> simple lists) >> > There is. It is https://github.com/. Just select any popular module from > simple lists available, for example > connect<https://github.com/senchalabs/connect>. Then > dig it's source code until you definitely understand how it works. While > doing so you will notice some dependencies. Do all steps above foreach > dependency. And so, and so, and so. Then select some good coders and follow > them. > > Node (and javascript) has one relatively specific feature. Because of it's > asynchrony model, javascript fitness for it and javascript goodness in > general it's extreamly easy to develop both low and high level modules. > Because of this we have a numerous modules doing similar things with > relatively similar quality. I guess this will not change in near future. > And this is a problem, especially for newcomers. But how comarison list can > help to solve it? It will just scare you even more. Node has extreamly flat > learning curve these makes learning through programming and looking at > third party code a real pleasure. > > On Friday, April 13, 2012 12:23:33 PM UTC+4, djcoin [Simon Thépot] wrote: >> >> Hi everyone, >> >> it's been a while since I thought that the massive amount of javascript >> librairies (and node.js specific ones) need to get organized. >> >> In my opinion, and I think most will agree, the difficult part in >> learning JavaScript is not so much about the language (well, it takes time >> too!) but rather about having to grasp its vast, ever changing, ecosystem. >> >> Correct me if i'm wrong, but there is no real place/tool to help achieve >> this overlook (apart from some simple lists) and I think it would be a >> massive improvement to have one. >> >> I took a few minutes to write this mail because I came accross this tool: >> http://opencomparison.org >> What about using or get inspired from this one, for JavaScript ? >> >> >> Second discussion: >> given javascript has no 'batteries included' - so it is not maintained by >> a core team - maintainers of each package are given much responsibility. >> They must be responsive and open to change, it is of vital importance if >> we want to avoid massive forks. >> >> I suggest the reponsability of maintaining, making evolve a lib should be >> spread among the community to ensure that. Details have to be discussed ! >> Here is a link on discussion currently taking place in the pyramid >> community to go that way: >> https://groups.google.com/forum/#!topic/pylons-discuss/SEHfJDrd5Fs >> >> >> What do you think ? >> >> Cheers, >> Simon >> > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > > > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
