The Problem with Responsive Frameworks
In an interview on responsive web design with .net magazine, Aaron Gustafason shared this thought on responsive frameworks:
I agree wholeheartedly with Aaron on this.
I learned quite a bit from digging around in the code of Bootstrap and Foundation, but for production projects, there’s just so much bloat and customization that needs to happen. I found myself removing code and wondering what I would break in the process.
And that’s why I built Kraken.
There’s a happy medium between using a full-featured framework and starting from scratch on each project. I believe Kraken fits nicely in the middle. I like to think of it as a boilerplate-plus. It’s a barebones, style-agnostic starting point, with a bunch of optional pieces you can add in and customize as needed.
Building blocks for developers. A library. A boilerplate. Faster than starting from scratch, but without the bloat of a framework.
Hat tip to Rian van der Merwe