It is an absolute non sequitur because there are plenty of languages that do not have the diamond dependency problem and are still based on the lambda calculus

It is an absolute non sequitur because there are plenty of languages that do not have the diamond dependency problem and are still based on the lambda calculus (and on symbol tables, which as it happens is pretty much not required by the lambda calculus at all, that's kind of the whole point of alpha-conversion and beta-reduction). Rust, for instance, will happily let you import two different versions of a library in your dependency tree, and just treat type definitions from each as different types. You get non-baffling and predictable (but still annoying) compile-time errors when library B and library C try to pass an object from library D between each other while requesting different versions. Rust also will happily let you define lambdas.