Addressing business needs is mostly orthogonal to implementation. One minute you advocate for continually drive improvements, and the next minute you throw Ruby under the bus because using it is somehow reinventing the “whole damn thing”? WTF? It seems to me you cast Ruby as a “toy language”; one that is not really suited to solving real problems. You are wrong in so many ways, its hard to know where to begin.

Also, I don’t understand you you could possibly confuse implementation languages and platforms for interoperability. You are smarter than that, Darrel. I know that you know that a solid architectural design will solve way more interop problems than having a consistent language/platform.