I disagree partly.
i would not call every framework nowadays just clutter, since frameworks with bad APIs already lost a lot of influence in the last 10 years.
libraries are not written only by single individuals, they have communities behind them.
however, what the typical cluttered "framework" of yesterday was, becomes more and more the "CMS" of any sort. Thats an example, why you should not use php "frameworks" - because they are not frameworks.
django however is well made, you can use it as libraries and set it up as thin framework in nearly every python app, taking your ORM with you anywhere you go. Since I DID do database stuff by myself, I would say: dont think in frameworks, if the project ist PERSONAL. Since in personal projects, your aim is to be creative and learn. frameworks should not be learned, they should be fastly usable.
And thats where I draw the last conclusion: frameworks have improved, because many of them offer a fast "first glimpse" into their apis and coding styles, and do not try to invent a new code style alltogether. e.g. many say prototype is better in its core API than jquery. but jquery is hell of easier to learn, since it does not modify javascript too much.
Use frameworks and libraries as much as you can in your daily work - dont let pride stay in your way, but do not use it for your creative work - dont waste your time learning how to modify something big, if you just want to create something new.