4 ms·
Depends where they come from. The average Python or Perl library seems better written and more tested that something I would write myself. JavaScript seems to h
by collyw 12y ago
Depends where they come from. The average Python or Perl library seems better written and more tested that something I would write myself. JavaScript seems to have a lot less quality in my experience.
- GrinningFool 12y agoI was thinking about that in response as well; then I began to wonder. Is it that the quality is actual higher, or that I'm more likely to gravitate towards established, well-tested libraries (of which there are fewer in javascript)? The more I think about it, the more I think it's the latter. There are tons of crap libraries out there for any language - but the more mature languages/ecosystems naturally tend to have a wider selection of more mature libraries.
- jmspring 12y agoThink about node modules. How often have you done an n install only to have 10+ other libraries brought in. Some are going to be decent, some not. I've found oddities like improper implementations of http digest auth and what not. When libraries are small you can sometimes catch these things easily.
- jnbiche 12y agoAs someone who prefers Python to JavaScript (as far as dynamic languages go), but who has been recently using nodejs a lot, I disagree. I've found that there is a very strong testing culture among node hackers. In my opinion, the biggest security liabilities in Node are with npm: 1. The culture that emphasizes tons of tiny packages, each bringing in dozens of other dependencies managed by multiple maintainers. The increases the attack surface dramatically. All it will take will be one single maintainer of a small package used by dozens of other packages to expose his npm password, and exploit could easily spread to hundreds of node apps in a very short period of time. I'm surprised this hasn't happened already. 2. On a related note, npm's lack of package signing. Most of the other popular dynamic languages (Python, Ruby, Perl) offer or even require package signing. npm does require SSL, but package signing is even more important, since only package signing can prevent the scenario I describe above. That said, I do see lots of unit testing in node packages, so I can't criticize them there.