That said, poor development - regardless of language - leads to exactly what you described.
And OO doesn't overly complicate stuff
I like automation. Don't really want to be coding record lengths and block sizes and alignments in some combination of JCL and COBOL. But
I am in the over 50 crowd. That said, I'm using SAS (all-time favourite cross-platform language, with a nod to Java for trying to take that title
I have a pet theory, that new languages are developed when some n00b starts in one language, curses it for not being able to easily do what they want, and creates their own
I remember the first time I hit VB
Who here has played with Panvalet? Yeah, originally designed before mainframes even had 'PDS's (folders) - so it offered a pseudo-PDS, and VSAM files couldn't be over 4 Gb - which it had a work-around for. Eventually, the underlying technolgy (IBM) incorporated those items. By which point Panvalet had a spectacular version control. Who here is using a *separate* version control tool? Currently playing with Tortoise SVN
There's this idea that technology can replace the need for skills. Seems to be prevalent in upper management, and in any company pushing their technology. And
Currently dealing with a large push to HADOOP. Woo! New buzzwords! How's that line go? "All groups develop their own language of obfuscation, to show who is, and isn't, in their group." Minor details like database design are completely alien to the group putting it together. Normalization? Huh, what's that? Slight problem in that at least two of the data feeds are both huge, and contain massive duplication. One system (M$ SQL Server) is already dying, because the same group didn't bother with any of those pesky considerations
I *don't* know that there is any driving need to stay with COBOL. Apart from - generally - it is easier to modify a well-coded COBOL system, compared to nearly anything else. That said, how many 'well-coded' systems are there?
It's like assembler. If you know what you're doing, one can code stuff to run faster. But, is it really worth it? The extra time spent in dev. The steep learning curve when bringing new people in. The near inability to do any coding in it without near toxic levels of caffeine in your system.
A lot of the complaints - and desire for 'new' technologies - have far, far less to do with the language/technology itself, and more to do with how well - or poorly - the previous system was implemented.
There's another quote I love - There are two kinds of fools: those who say 'We've always done it this way, so that is best', and those who say 'This is new, so it must be best'.