While we all know that ruby gems have a couple of issues I think one thing was done exactly the way it should be - somehow enforced standard structure: NAME.gemspec, bin, ext, lib, lib/NAME.rb. I don't know if this is specific to only ruby community but there is at least some level of consistency which makes everyone lifes easier.
I will have to carefully read all arguments agains enforcing such structure in bower.
There are various solutions to managing assets in a rails application but we didn't like any of them. The one you linked to requires having separate list of dependencies and using bower directly which means hacking standard rails deployment.
Love it. Keeping JavaScript libraries up to date in Rails can be a real pain and the sprockets solution just isn't all that great. I like how you have approached this with a dead simple approach to implementation and integrating with the existing tooling (bundler/Gemfile). Good work!
This doesn't replace Sprockets at all, but integrates with it. It replaces bower "installer" with a pure ruby dependency. Sprocket still handles the runtime operation.
joshpeek, I wasn't suggesting this replaces sprockets. I was saying that the sprockets/bower integration out of the box isn't all that great, and this seems like a useful tool to help improve the situation of a common problem.
I will have to carefully read all arguments agains enforcing such structure in bower.