Why “Polyglot Programming” or “Do It Yourself Programming Languages” or “Language Oriented Programming” sucks?

Last year we saw the launch of a new Web programming language Dart - Structured Web Programming from Google. A very interesting approach to support web application development. Not so long after Go, Groovy, Ruby, Scala, << Name your DSL here >>; we see Dart. Is it a good thing to have at least one programming language to solve one problem? The answer is, like we already know, it depends.

Stay Away From “Do it Yourself”

It is your choice as to if you will try to do things yourself or allow the truly seasoned professionals to help out. Some decide that they are going to try to go it alone when they are programming something new, but this often ends up in a less than desirable place. It may even be more expensive than just hiring an expert who can help you get it programmed for you in the first place.

Defining Polyglot Programming: Podcast With Neal Ford

Polyglot programming, whilst not a new concept, is becoming increasingly relevant to full-stack developers and to microservice architectures. That’s because it allows a developer to mix and match programming languages to suit their personal preference, expertise, or the functional requirements of the project.

ThoughtWorks Director and Software Architect Neal Ford joins me and David Brown in this episode as he discusses the benefits of polyglot programming, a phrase he originated himself. He also shares how developers can use this practice in making application development more efficient, and how the concept of low-code is relevant in all of this.