The Infrastructure Effect: COBOL and Go

Published: Aug. 20, 2019, 7:05 a.m.

b'Languages used for IT infrastructure don\\u2019t have expiration dates. COBOL\\u2019s been around for 60 years\\u2014and isn\\u2019t going anywhere anytime soon. We maintain billions of lines of classic code for mainframes. But we\\u2019re also building new infrastructures for the cloud in languages like Go.\\n\\nCOBOL was a giant leap for computers to make industries more efficient. Chris Short describes how learning COBOL was seen as a safe long-term bet. Sixty years later, there are billions of lines of COBOL code that can\\u2019t easily be replaced\\u2014and few specialists who know the language. Ritika Trikha explains that something must change: Either more people must learn COBOL, or the industries that rely on it have to update their codebase. Both choices are difficult. But the future isn\\u2019t being written in COBOL. Today\\u2019s IT infrastructure is built in the cloud\\u2014and a lot of it is written in Go. Carmen Hern\\xe1ndez Andoh shares how Go\\u2019s designers wanted a language more suited for the cloud. And Kelsey Hightower points out that languages are typically hyper-focused for one task. But they\\u2019re increasingly open and flexible.'