Observation 1

When you pick a framework, you need to evaluate how “good” it is to your use case.

If you’re like me, you don’t want to spend a lot of time “evaluating” it. You also don’t want a framework that’s a “bad choice” in the future. A framework that is rigid to give you the features you want but also flexible to allow you to build. Non opinionated but also able to give you the convience you want. You can see a lot of value clashes here. Reality says you can not have both; you MUST pick. But picking means you, an uninformed individual must make an informed decision on a framework you have minimal exposure.

My solution is easy. Pick one that you can most easily is “suitable to your present needs”. It’s a braindead solution.

Too often, trying to predict your project’s future is a foolish task and then to hinge your present choices on that is a food’s errand. Premature optimization is evil.