30 ms·
Look at the trails Node + NPM have blazed. That's the right move. Next up: Local package installs.
by arturadib 13y ago
Look at the trails Node + NPM have blazed. That's the right move.
Next up: Local package installs.
- dangerlibrary 13y agoI don't think effective package management solutions were really pioneered by node and NPM. You could pretty easily re-write your comment and say "Look at the trails Debian + apt have blazed. That's the right move."
- knappe 13y agoOr, for a more apt (heh) comparison: https://github.com/rubygems/rubygems https://github.com/rubygems/rubygems
- jjwiseman 13y ago"If you are writing a package manager for a new non-js language, do whatever it takes to get that new language to load modules the way node does. The right way." http://dominictarr.com/post/25516279897/why-you-should-never-write-a-package-manager http://dominictarr.com/post/25516279897/why-you-should-never... http://dontkry.com/posts/code/modules-the-right-way.html http://dontkry.com/posts/code/modules-the-right-way.html To be more specific, what npm does that pip, debian, and rubygems don't do is nested dependencies, which is a wonderful advancement.
- mbreese 13y agoIsn't virtualenv going to be bundled too?
- tbatterii 13y agoa flavor of virtualenv was bundled in 3.3 (http://www.python.org/download/releases/3.3.0/ http://www.python.org/download/releases/3.3.0/) but without pip or easy_install it was a pretty useless feature IMO.
- riffraff 13y agorubygems has been bundled with ruby since 2009, and perl has had cpan since about forever.
- pekk 13y agoPython has had a good installer forever. The only difference is that it wasn't centrally mandated. If you need something to be centrally mandated in order to use it, I feel for you.
- recursive 13y agoIt does help to know that it exists.
- njharman 13y agonpm badly re-implements what others have done dozens of times. The whole node ecology suffers heavily from "not invented here" syndrome.