Re:Why JavaScript Will Become the Dominant Programming Langu...
by WalterSear on Monday September 02, 2013 @02:53PM
(#6316521)
A recent nodeup episode discussed how many enterprises aren't using npm packages unless they wrote them in house, because they don't want/trust any code they haven't written themselves.
[ Parent
| on HN ]
Re:Why JavaScript Will Become the Dominant Programming Langu...
by jmspring on Monday September 02, 2013 @03:54PM
(#6316815)
I've also seen other companies who do use third party modules through npm make sure they have local copies documenting the version, source, source url, etc. Just in case a particular project disappears.
One thing I wonder about, so far it seems to be mostly doing ok, but will NodeJS suffer the library versioning problems that plagued Java when I last used it...frameworks importing 2-3 different versions of Apache Commons for instance.
Re:Why JavaScript Will Become the Dominant Programming Langu...
by mattschmulen on Monday September 02, 2013 @04:25PM
(#6316996)
Seems like 'in general' this is a good practice. you need to know 'what's inside' if your writing bank, finance, health-care, etc ... apps on top of other peoples code. besides as a developer you want to make sure running 'npm update' does'nt change a foundation library in a negative way. the best practice in enabling this is still up for dispute.