> But let’s be straight, that’s like 1% of all of the developers out there — the rest of them are just lurking and coding with their language of choice and being content with it. Be it Fortran, COBOL, Perl, or PHP. Assuming all developers who are using something like COBOL or Perl are content with it is hilarious. It doesn't really get much worse than something like COBOL or Perl in terms of ergonomics and ease of us…
COBOL, on the other hand, is a domain-specific language for a domain most people here have no experience with: Software involving fixed-format input and fixed-point numerical calculations. It would be amazing if some language integrated a clear way to describe modern, recursively-defined input formats with the same degree of language support COBOL has for its data definition language. Go is still too verbose, sadly.
Fortran suffers from FORTRAN, by which I mean if you mention Fortran to people they think of 1960s-era mainframe software with no string support, column-oriented fixed formatting, and GOTO use by people who'd never even heard of Dijkstra. Modern Fortran is not like that; sadly, much like Lisp, they never changed the name, so old ideas linger. (This is also true of Cobol.)