That's probably historical, but I wonder what's the point to advertise that the cluster supports Cobol for example?
That's probably historical, but I wonder what's the point to advertise that the cluster supports Cobol for example?
A friend of mine works on a COBOL system that's responsible for calculating pension payments for former government employees. COBOL is good enough for this application, since it's basically just a glorified pile of if-statements.
Rewriting everything in the hot-new-language-of-the-year would almost certainly introduce bugs, so instead of screwing up people's pension checks every couple of years, they just pay a my friend to know COBOL and to keep the rules up to date.
There's still enough of a community behind COBOL that there's really no reason not to do this. COBOL compilers continue to be maintained, and even the language itself is getting updated (see e.g. https://en.wikipedia.org/wiki/COBOL#COBOL_2014).
Yes, that's the point I usually hear. I.e. that it's used for legacy applications, just because switching to anything else doesn't worth the effort. I'd be more surprised however when it would be used for any new project.
That's of course understandable (for keeping legacy systems), but new systems deployed with using Cobol is not so expected.
Once your experience in development evolves beyond buzzword-bingo web apps and obsession with faddish language features, you find all sorts of real work being done in uncool things like Cobol, Ada, Fortran, VB, etc.