Este documento procura manter referências importantes sobre o conceito de Programação Poliglota.

• Welcome to Polyglot Programming: Polyglot Programming is a website dedicated to exploring the benefits (and drawbacks) of combining multiple programming languages and multiple “modularity paradigms” in application development. The “paradigms” include Object-Oriented Programming, Aspect-Oriented Programming, Functional Programming, etc.

• Dean Wampler's Blog
• Polyglot Programming: Applications of the future will take advantage of the polyglot nature of the language world. We have 2 primary platforms for “enterprise” development: .NET and Java. There are now lots of languages that target those platforms. We should embrace this idea.
• QCon - Radical Simplification through Polyglot and Poly-paradigm Programming: Segundo Dean o maior problema daquilo que definiu como monoculturas é que geralmente há mais código do que o necessário - o que ele definiu como the pervasive IT problem – e que a razão para isso é o uso de linguagens ou paradigmas não ideais para o problema sendo resolvido.
• Polyglot, not Panglot or Omniglot: In fact, just because polyglot programming as a strategy means you will use more than one language, it is even more important to be careful and use the best languages available for the task. Which is why I’m working to improve JRuby, why I’m evaluating Scala as a replacement for Java, why I’m working on a language based on Io. It’s all about using the best languages. I may be a polyglot, but I’m definitely not a panglot or omniglot.
• Connecting Languages (or Polyglot Programming Example 1).
• A New Hope: Polyglotism: I guess that’s the message of this post. Compare languages, understand your most important tools. Have several different tools for different tasks, and understand the failings of your current tools. Reason about these failings in comparison to the tasks they should do well, instead of just comparing languages to languages. Be good polyglot programmers. The world will not have a new big language again, and you need to rewire your head to work in this environment.
• Fractal Programming: The core of these ideas are based on polyglot programming, the thinking that you should use several different languages in a project, based on which languages are better suited for different parts of it. Another term for this concept is Language-oriented programming. So how do you organize a polyglot system? The most natural way for me is to divide it into layers. In most cases you will find that different categories of languages will be better suited to different layers of the application.
• Even more than Polyglot programming: After hearing Neal’s speech it occurred to me that the separation of languages we force ourselves to do is really unnatural. Writers don’t do this with the written language because it is too restrictive. Historians and journalists will often freely mix philosophic prose with cold hard statistical facts for example. Tolstoy mixed languages because he understood that sometimes a language can express something more effectively, expressively, succinctly, etc… than other languages.

• Beware of polyglot programming

• Article: Paradigm based Polyglot Programming: Have you ever wondered why people talk about having “the right language for the right job”? Or why people talk about using more languages within the same system? In this article, Sadek Drobi explains why you should consider mixing languages within you system. Sadek explains how different languages support different kinds of problems better (or worse) due to the nature of the language and the nature of the problem.
• Paradigm based Polyglot Programming: To be able to do the right decision one should keep in mind that the main reason of adopting polyglot programming is to be able to choose the right programming language for the domain problem at hand. But then, the question is how to choose the right language for a given domain or sub-domain?
• Polyglot Programming: Is it just too much to ask?
• Polyglot Programming: Is building applications with multiple languages a good practice?
• Don't Fear The Poly-Headed Polyglot Monster: In 2008, the polyglot programming paradigm is still (at least in my opinion), a relatively novel concept. There aren't a lot of resources to show us how to do it the right way. As time moves forward and people publish their experiences, that should be expected to change.

• How Do You Apply Polyglotism?: For the past two years or so, there has been an increasing meme across the developer blogosphere encouraging the application of the polyglot methodology. For those of you who have been living under a rock, the idea behind polyglot programming is that each section of a given project should use whatever language happens to be most applicable to the problem in question. This makes for a great topic for arm-chair bloggers, leading to endless pontification and flame-wars on forum after forum, but it seems to be a bit more difficult to apply in the real world.
• Polyglot programming: Thus, writes Ottinger, the Java platform itself can be used as a launch point for polyglot programming, after a sense, in that you can write modules in various languages (JavaScript, Ruby, Python, Groovy, BSF) and use them from within a Java framework and on the Java platform.
• Polyglot programming on the Java Platform.
• Polyglot Programming with Groovy

• Polyglot Programming: While some question the need for multilanguage support, .NET proves that such strange bedfellows as Fortran, Eiffel and C# can interoperate. First in a three-part series.
• Building Solutions by Composing Languages: This article delves into the motivation, benefits, and challenges of writing applications using polyglot programming—leveraging the multi-language nature of the CLR to create simpler solutions to vexing problems.
• Polyglot Programming: Building Solutions by Composing Languages: Polyglot programming refers to leveraging existing platforms by solving problems via solutions that compose special purpose languages.This concept leverages the multi-language nature of the CLR to create simpler solutions to vexing problems. This article delves into the motivation, benefits, and challenges of writing applications in this style.

• The Polyglot Programmer - Mixing And Matching Languages: There's always a cost to taking a polyglot approach, of course: debugging a polyglot program can be more difficult than debugging a monoglot one, owing simply to the fact that now the developer must speak two (or more) languages, rather than just the one.