Most organization have a Java and/or .Net team. For a while, I had a few people for Cobol only for troubleshooting and maintenance. For the given deptartmet budget I cant have an additional Cobol team for either application development or infrastructure work only because Cobol does batch jobs very well. Every single of our batch job was run using Java, ant, xml on a CI box and they did a fine job.
A tiny advantage here and here isnt worth a huge investment in a legacy system that comes with its own share of nightmares. You would know that only if you ever worked as a manager or tech lead.
I have. I'm now a program manager. And I've worked across not only web-based apps but mainframes, erp systems, bi systems, messaging connections between these and others.
A tiny advantage here and here isnt worth a huge investment in a legacy system that comes with its own share of nightmares -- you are incorrect. And I can assure you you are very incorrect. M/fs may be considered legacy but in enterprise batch data they rule.
Don't come here as a pm for a web-page and talk about that as if all apps should conform to that level of slap and dash.