There’s way too much variance in projects for the average to be meaningful, in my opinion. They will have some or many average parts, but they will also have so

There’s way too much variance in projects for the average to be meaningful, in my opinion. They will have some or many average parts, but they will also have some number of parts that are special. It might be normally distributed, but across tens/hundreds/thousands of dimensions. For example, some axes might be * resource usage requirements * latency * persistent storage options (filesystem/SQL/Redis) * concurrency needs * UI options * error handling technique * etc, etc Like, if you want a terminal-based UI and don’t need SQL access, then you definitely shouldn’t use Ruby on Rails. Some of those dimensions are obvious at the start of a project but some aren’t. You might not find out until later that you need something that your framework doesn’t support. And when that happens, you can end up in a situation of hacking together the feature working around the framework, especially if there’s a deadline. Like I said, frameworks are great if you are very careful with their limitations.