The problem with this as I see it is that you have to have a package manager (apt/yum) and install another package manger (npm) to install yet another package manager(bower).
It’s package managers all the way down
Actually I seem to remember npm suggesting that you should get it from source over apt/yum.
I wonder who is going to maintain it? Both @fat and @macman have left Twitter.
Maybe if jquery was broken into smaller modular parts ala Ender, then it would make sense.
I think it’s a little bit of a chicken-and-egg problem. As a framework author, I’d love to be able to provide Ember.js in a more modular format to our users—but it’s such a pain in the neck right now, we basically have to distribute it as one file. If it was trivial for people to assemble different packages, we’d be happy to support it. In fact, we specifically architected Ember.js in this way (just look inside our packages directory); we’re just waiting for a sufficiently sophisticated package manager to appear.
Do you consider BOWER to be a sufficiently sophisticated package manager?
No, I don’t think it is, and I’ve had several meetings with Alex and Jacob trying to convince them of it. In particular, I don’t think using git as a mechanism for package management is anywhere close to a good idea.
You really want the ability to query a central repository for a changeset, instead of what Bower does, which is query GitHub once for every package and its dependencies. After the rubygems.org server made this change, installing gems went from an annoyance to a process you barely notice anymore.