By Joe Brinkman on
4/1/2009 4:36 AM
In 2006, Neal Ford wrote a blog post on the topic of Polyglot Programming which foresaw a future where applications will be increasingly built using multiple general purpose languages and domain specific languages. Ted Neward has a recent article from MSDN Magazine which follows up on this theme with a discussion of Polyglot Programming in .Net. Both Neal and Ted address some of the issues with Polyglot Programming, but I think there is one that they have missed. Polyglot Programming can quickly lead to performance rot in application development.
In DNN Tips and Tricks #10, I presented an example of how you can use the DotNetNuke Report Module to display you data using the advanced capabilities of XSLT. Greg Lahens pointed out an issue with my SQL code which is really highlights one of the downsides to Polyglot Programming. As programmers, we often employ a variety of tools to solve a particular programming challenge. Many of these tools are DSLs – XSLT, SQL, CSS, HTML are just a few of the many DSLs in common use throughout the web development world.