COBOL was right for the times. The compilers produced small efficient programs that could produce payrolls for 25,000 employees on a computer with 64kbyte and an instruction time of 2us. Because of the verbosity, it wasn't difficult to maintain. Not quite self documenting like Grace Hopper wanted, but close. The PIC(ture) reservation of memory is better tuned for portability than most languages because it described what the programmer really wanted rather than what the machine provided. I want to store up to a million dollars as credit or debit, in a computationally efficient manner, PIC S999999.99 COMP. And let the compiler figure out how to deal with that in whatever architecture it ran on.
Many people criticise COBOL for being slow to write, due to the verbosity. I haven't written a COBOL program for over 30 years, but in the day I could churn out between 200 lines a day to 100 lines an hour. Like any language the effort is in translating the ideas into actions and it doesn't really matter in what language that action is expressed. For one employer I wrote programs that were COBOL, FORTRAN and Assembler composites to take advantage of the computational features of FORTRAN, the ease of laying out a report in COBOL, and Assembler routines to compress and decompress records being written to and read from magnetic tape.
Today such efficiencies are no longer prized. Throw more memory and a bigger processor at the task. The C language changed a lot, now the choice for more efficient programs. And if efficiency is subordinate to productivity , choose the language appropriate to the task at hand. The worst programming language is the one that gives the most grief trying to translate ideas to actions. It may be possible to compute satellite orbits using COBOL, or write invoices using FORTRAN. Who would want to.