It would be interesting to see someone go through a public repository and compare error rates / bug fixes between dynamic and static languages implementing the same kind of products. Might not point out differences in the approach but at least in the entire ecosystem (tools+developers+code).
At a certain distance you can swap the approaches anyway (but for syntax):
static as dynamic: Use Thing = HashMap<String, Thing> instead of objects.
dynamic as static: Put assert(type(x)=="int") everywhere.
As to building large apps. If you need to build a large app (ie you cant divide it into isolated subsystems) then your goose is already well and truly cooked :)
At a certain distance you can swap the approaches anyway (but for syntax):
static as dynamic: Use Thing = HashMap<String, Thing> instead of objects. dynamic as static: Put assert(type(x)=="int") everywhere.
As to building large apps. If you need to build a large app (ie you cant divide it into isolated subsystems) then your goose is already well and truly cooked :)