I decided to take a break from re-working my wife's website (side/for fun project) and stumbled upon this submission. Ironically, I was just wrestling with how

I decided to take a break from re-working my wife's website (side/for fun project) and stumbled upon this submission. Ironically, I was just wrestling with how to migrate my pure CSS bootstrap implementation to a semantic ui with Less. Bootstrap is NOT built for abstracting away it's implementation details even if you use Less...I can't get rid of a collapsible nav or input-group-addons. I wish I had a mixin for each... The author is spot on with his concerns, but I think there is one more to the bower equation. Why does the package manger have to pre-build their assets for me to use them? Why can't I use the grunt files associated with the bower project I imported to build my assets? Let's imagine there is a scenario where I create some sort of grunt config which includes/excludes certain bootstrap js files (I'm assuming that 1) grunt allows me to extend/overwrite the package's variables 2) I can chain the grunt builds of multiple dependencies together...then when I build my project, I only get what I configured.