I like Twitter Bootstrap but there are a number of challenges when it comes to being productive. (forget responsive.) What happens when you spend 6 months building your killer Bootstrap killer app when out of left field there is a new release. Whether it’s a patch or a feature release is not the challenge. But what happens when you purchase a template from a vendor and that also needs an upgrade. Can it be as simple as a drop-in replacement? I don’t think so.So when you buy one of those templates from wrapbootstrap you should plan on being in front of your keyboard when they upgrade. The only way this will work well is if there is a loose coupling between your client-side components and the bootstrap artifacts; and as far as I can tell; that simply does not exist.