4 ms·
JavaScript seems to be having the same problem that other languages have developed over usage time. It becomes increasingly difficult to know what package does
by hsmyers 14y ago
JavaScript seems to be having the same problem that other languages have developed over usage time. It becomes increasingly difficult to know what package does what and more importantly information of the pros and cons of the package. Does anyone know of a link to something similar to what I'm talking about? Say something meaningful about the top N (where N might be 10 or so) packages---what they do, the good and the bad?
- mnutt 14y agoCheck out the Node Toolbox: http://toolbox.no.de/ http://toolbox.no.de/ It doesn't seem as fleshed out as the Ruby Toolbox (https://www.ruby-toolbox.com https://www.ruby-toolbox.com) and could use a bit more editorial for your purposes, but it's a good place to start.
- bmelton 14y agoThanks a ton for posting that. I'm new to Node, and it's a great help. Of course, it'll never go anywhere until whomever is maintaining it either allows for crowdsourcing of the data or tries harder, because the first couple of packages I looked at had very poor descriptions. Coffeescript, for example, is defined as "Unfancy JavaScript". CS is one that I happen to know about, and by that definition, I'd have never ever switched to it.
- yesbabyyes 14y agoPeteris Krumins had a nice series of Node.js modules you should know about: http://www.catonmat.net/category/nodejs-modules http://www.catonmat.net/category/nodejs-modules Some of my favorites: - async -- flow control - stitch -- packaging client side scripts - express -- web framework - redis -- great Redis client - stylus -- css preprocessor - request -- HTTP client I find myself following certain people, like how I'm a fan of different rappers. Usually, stuff by visionmedia, felixge, mikeal, isaacs, substack is top notch.