News for hackers. Stuff that matters.
Re:The Node.js Community is Quietly Changing the Face of Ope... by mtrimpe on Tuesday April 16, 2013 @09:49AM (#5558002)
Can anybody tell me what NPM does that e.g. Maven / CPAN / Gems e.a. don't?

I haven't seen anything in NPM so far that goes beyond Maven's capabilities so I'm really curious what NPM's big advantage is.

Re:The Node.js Community is Quietly Changing the Face of Ope... by karterk on Tuesday April 16, 2013 @10:31AM (#5558267)
Let's say your application depends on two libraries A and B. And let's say that these 2 libraries depend on different versions of library C. In Maven if library C is not backward compatible, you're stuck. Only one version of library C can exist in the classpath and so one of your 2 libraries might fail. However, in node, library A and B use their corresponding versions of library C. There are no conflicts.
Re:The Node.js Community is Quietly Changing the Face of Ope... by josephagoss on Tuesday April 16, 2013 @11:20AM (#5558619)
This is amazing. I'm actually surprised NPM is one of the few that gets this right. I guess we are still in the early days of Software engineering.
Re:The Node.js Community is Quietly Changing the Face of Ope... by pmahoney on Tuesday April 16, 2013 @11:27AM (#5558669)
No conflicts, but a tradeoff of loading two versions of library C. I assume at some point, the cost of multiple versions of everything (in terms of memory usage, for example) becomes an issue?
Re:The Node.js Community is Quietly Changing the Face of Ope... by mayank on Tuesday April 16, 2013 @11:54AM (#5558853)
That's the tradeoff, with the crux being that adding more memory for a bit of JIT-compiled bytecode is preferable to having an app that just won't work.
Re:The Node.js Community is Quietly Changing the Face of Ope... by pekk on Tuesday April 16, 2013 @04:21PM (#5560636)
There is something to be said for requiring developers to make things work right rather than work around their screwups, however.