Most of these disadvantages are actually not a big deal. If your app is so simple that this is a reasonable choice, it's probably trivially easy to do with a fr

Most of these disadvantages are actually not a big deal. If your app is so simple that this is a reasonable choice, it's probably trivially easy to do with a framework. The idea that frameworks restrict you seems like an XY problem. They block you from doing one thing, but that's because there's already a specific idiom for that. When you're really "thinking with frameworks" you don't even think of doing X. The framework becomes your language and you design everything in terms of it. I would also argue programmers are not lazy, but they should be if they want to get stuff done. Programmers like to tinker with random stuff and take things apart to see how they work. They'll gladly do 2x the work for half the performance if it means a solution they understand.