A framework is like a Leatherman. It’s a prescribed approach that will work sort-of-ok for a wide array of problems. This is very useful in some situations, such as when you’re not sure what you are building (very early prototyping), when you are a junior developer just starting out, or if you are leading a team of junior developers that needs structure to work in an aligned manner. If you’re in this situation, it really does not matter much what framework you use. Just pick the one that you (or your team) is most familiar with, because that is the one that will lead to the least bugs and highest speed.
To be clear here, I’m separating the concepts of frameworks and libraries here. I’m not advocating building your tooling from scratch, I’m talking about picking and choosing multiple, specialzed tools for the job, instead of trying to solve everything with a big, general one. In the carpenter analogy, a framework is a Leatherman and a specialized library is an electric screwdriver.