Bower for package management, it makes sense now

I finally see the point of using Bower for package management for front-end web development. It’s made for larger projects where you’re going to be upgrading components every few months and the dependencies really need to be managed for that.

I’ve worked on relatively small web sites and web applications that aren’t products, they’re projects and usually short-term. They will typically only require one version of 1-5 different javascript libraries and only a few CSS components. There’s usually no upgrading of any javascript or css libraries at all, at least not until a new project is started.

In those types of projects, Bower is overkill. The project won’t last long enough or be large enough to see any benefit from the use of Bower.

But for the larger projects, the sites that will last for many months or years, the products that will need to be supported and updated over the course of a few years, you require package management.

While I may be sold on the necessity of Bower, I’m still not sold on the use of Grunt as a front-end build tool and think that Makefiles are great and that you should aim to integrate your front-end build cycle into whatever back-end build tool is available. The new Web world is scary with all these new ideas, but most of them are old and some of them do make sense (like Bower…but not Grunt).

One Comment to Bower for package management, it makes sense now

  1. […] tried using grunt before (I mentioned it before) and haven’t been able to wrap my head around it and why it’s useful. GNU Make is still […]