The choice of a package manager is on a project by project basis. It's not as if you were required to use Bower or NPM to manage your dependancies. Those are s

The choice of a package manager is on a project by project basis. It's not as if you were required to use Bower or NPM to manage your dependancies. Those are simply two tools used by the JS community to manage its dependancies. There are a lot[1] of them. Where I work, everything was pushed by the back-end guys for a long time. This made the front-end developer dependant on them. With tools that use front-end languages (JavaScript), the front-end team is now free to experiment with package management and build systems (Grunt.js, Gulp.js). This made it so that we now have a very complex but quick and useful front-end workflow. We wouldn't have this if we had not freed the front end team dependancy on the back end team for builds, dependancies, etc. [1] https://www.npmjs.com/ https://www.npmjs.com/ http://bower.io/ http://bower.io/ http://duojs.org/ http://duojs.org/ http://webpack.github.io/ http://webpack.github.io/ https://github.com/componentjs/component https://github.com/componentjs/component http://enderjs.com/ http://enderjs.com/ http://jamjs.org/ http://jamjs.org/ http://volojs.org/ http://volojs.org/ etc.