Why I don't use frameworks
I don’t use frameworks, and rather than use one yourself I’d recommend making your own.
Frameworks are useful for speeding up the production of a project, once you’ve learned them. But until then they’re slow to use (because you’re working it out), hard to debug (because you’re working it out), and can limit your design - because you will end up altering the design to fit what you can do with the framework at the time.
Fine and dandy, but once you know one you don’t have those problems. You have others instead though, because you’re stuck with whatever limitations it has built in. All techniques (and frameworks, which are just a big collection of techniques) have a flaw somewhere - be it classitis, an inflexible grid systems, dictating mark-up, bloated file-size, or any number of other factors. If you only know that framework, you’re stuck with whichever drawbacks it has.
It’s far better in my opinion to learn the techniques yourself and make your own systems/framework. That’s why I do not use any frameworks even though I do look at a few to see what ideas and techniques they’re using. If I learn something new from one, I’ll usually incorporate it into my own personal “framework” (I use the term lightly, this is a starting point for new projects, not an all-things-to-all-men framework).