Re:When Node.js is the wrong tool for the job
by imagist on Friday January 06, 2017 @10:07AM
(#13336780)
Integrating a library requires a lot of thinking, or you'll integrate libraries that are immature and break, or don't exactly fit what you wanted and have to be hacked around. I've had to work in projects that used your methodology long-term and I would rather turn down a job than suffer through that again.
Re:When Node.js is the wrong tool for the job
by RUG3Y on Friday January 06, 2017 @11:09AM
(#13337390)
What do you mean by "package-completeness"?
While npm has a lot of packages, Python has a lot of fully matured, well-tested and well-documented packages.
It's apparent to me that there are a lot of low quality, duplicate and otherwise unstable npm packages.
Don't get me wrong, I actually like npm too but I don't think the Python comparison is even in the same ballpark.
Instead of writing "a quick Python script" for personal use, I now write "a quick node script" because there's almost no thinking required on my part. Just require the packages and throw them together.
Not even Python has this package-completeness.