I was very much of that opinion before as well. But I've since come to change my mind. I'd like to concentrate on those parts that are unique about the application that I write, not the stuff that every application has to do anyway. This takes a lot of time and effort to maintain, especially if you want to stay 'current' and want to compete with the rest of the market.

If what you make is limited in scope and you can easily handle the worlkload then more power to you. But I find that for me it is more efficient to reuse well written code, even if that means I can't claim I wrote 100% of the project.

If a framework limits you, then that is a good reason to roll your own. But that comes at a price, maintaining a codebase is not without cost.