Just notice this op-ed piece where he says,

Down in the coding trenches, the worlds of objects and of RDBMSes and of XML are far from unified, and that attempts in that direction have been less than enthralling. I think we just have to get used to it, and from here on in, the practice of software engineering is a three-legged discipline.

I’ve noticed the same thing, and have come to the same conclusions…

For instance, when I created my XML components, I resisted the temptation to create an elaborate Java-oriented query mechanism based on DOM or some such, and just went with XPath as the way for accessing data within an XML file.

Similarly, all of my database access components have a property simply called “SQL Query” where I just enter the SQL statement directly. I have found it far more effective (not to mention just plain easier) to use both a language and its knowledge base that is oriented to the task.

I know many people who are mono-language-ists— who feel that everything in the world can be coded in Perl, or in Java, or in XML (have you see Jelly ohmygawd?) or in   insert language here  
. Of course you can write everything using the Borne shell, but why would you?