The New Stack @ Scale logoWhich programming languages are most appropriate for use in the cloud? That question, in essence, is the topic of discussion for the twelfth episode of The New Stack at Scale podcast, now live on SoundCloud and iTunes.

The format of this episode is a little different. First, The New Stack’s Scott Fulton presents a special segment on programming languages, particularly Go, in a cloud-native environment, with Red Hat Principal Software Engineer Vincent Batts, as well as Lead Software Engineer Chris Haupt and Product Manager Victor Soares from New Relic.

Then host Alex Williams (founder and editor in chief of The New Stack) and I are joined by “the famous Adron Hall,” a Portland-based developer working on issues related to scalability and deployment of large-scale systems, including DevOps, for clients like the Home Depot Quote Center. (Note that Adron has contributed several excellent programming posts to the New Relic blog. Check them out here!)

new stack @ scale podcast: programming languages discussion

Clockwise from top left: The New Stack’s Alex Williams, New Relic’s Fredric Paul, and guest Adron Hall.

Static vs. dynamic programming languages

Scott’s segment [time code 1:51] points out the differences between dynamically typed and statically typed programming languages in the “cloud native ecosystem.” In particular, the segment talks about the rise of Go, for which New Relic has just released a new agent. (Be sure to read Ready? Steady. Go! Public Beta of Go Support Opens in New Relic APM.)

Scott notes that since it was originally developed for Google’s internal use, Go seems particularly well suited to “help developers looking to integrate static server-side development with dynamic client-side development” in cloud native environments. Even though the Go community has grown significantly as companies like New Relic use it to build new products and applications—including New Relic Infrastructure—Go hasn’t yet barged its way into most programming language top 10 rankings [18:08]. (For more information, see The Most Popular Programming Languages of 2016.)

go gopherWhat’s next for Go?

According to Adron and Neha [26:11], that’s partly because Go is a relatively new language, and developers may be waiting for build-outs of more mature tooling, including IDEs and specific frameworks. More important, though, according to Adron, many traditional companies outside the San Francisco/Seattle/Portland axis of new internet companies are not yet living in the cloud-native, polyglot world of microservices architectures, containers, and multiple single-purpose applications that Go helps enable.

To put it simply: “As goes cloud, so goes Go!”

Listen to the entire podcast for much more on Go and cloud-native environments, including how long it takes to “jump on the Go train.”

New Relic is a sponsor of the New Stack @ Scale Podcast. However, the content and views expressed are those of the participants of the New Stack @ Scale Podcast, which is the property of The New Stack. Any views expressed on the New Stack @ Scale Podcast do not necessarily reflect the views of New Relic. By embedding the audio for the New Stack @ Scale Podcast or linking to The New Stack, New Relic does not adopt, guarantee, approve or endorse the information, views or products available on The New Stack site.

For more information and another take on the podcast, see Kiran “CK” Oliver’s post Has the Go Language Become Cloud Native?'

Fredric Paul (aka The Freditor) is Editor in Chief for New Relic. He's an award-winning writer, editor, and content strategist who has held senior editorial positions at ReadWrite,, InformationWeek, CNET, Electronic Entertainment, PC World, and PC|Computing. His writing has appeared in MIT Technology Review, Omni, Conde Nast Traveler, and Newsweek, among other places. View posts by .

Interested in writing for New Relic Blog? Send us a pitch!