What do you mean by "mix and matching"? I feel like a concrete example might help me understand what you're thinking of in this thread.

> Sure if you only do CRUD you probably won't run into those cases. Math heavy, scientific code, simulations, etc might disagree

Ha, it's funny because I've recently started doing more math-y / scientific / simulation work in python, after a career spent mostly doing CRUD-y things in not-python, and I've never been more convinced that it is best to make code as statically legible as possible. It's hard enough to make sure the math and the algorithms are right, I don't want to also be reasoning through dynamic abstractions.

But again, maybe there's a concrete thing you're thinking of here that I'm not seeing!

A bit of a contrived example, but think of multiple inheritance but dynamically.

> maybe there's a concrete thing you're thinking of here

Genetic programming would be the main use case of this (of table dispatch, not the "mix and match thing", which ok, is a bit of a corner case

> I've never been more convinced that it is best to make code as statically legible as possible

Given how the average academic code is, I don't think I can disagree with you much

And I think it's also a question of syntax. For those kinds of things a lambda might be more readable, but a typed lambda is still a lambda.