Ok will do. The summary of the site says "JavaScript development, HTML5, and front-end news" so I figured that since this falls under the other two, that it was acceptable.
This article didn't really address by bower exists, and why it's approach to dependency resolution is inherently different than NPM. If you use NPM and browserify, you could potentially end up with 10 copies of jQuery in your project, which is probably not what you want. If you cleverly use the shim you can get around this, but bower was designed to support front-end dependencies. Are there problems? yes. Is NPM the holy grail of package management? no, it's great for NodeJS stuff but not front-end. </opinions>