If you are a COBOL guy, doen’t get too upset because it all comes around. If you really want to see a language put down, read what the Ruby community or functional programming gurus say about Java (and C# by inference).
For the record, I have coded in Fortran 77 (badly) and worked in a shop mostly dominated by COBOL. I don’t have anything against COBOL per se, but I think the early versions discouraged the usage of subroutines due to inefficiency set back programming a bit. I jokingly called someone a “COBOL programmer” just yesterday for a big, big chunk of Java code unpolluted by fluff like other classes and extraneous methods (behind his back, but don’t feel sorry for him, he makes much more than you or I. Non-coding architect having fun learning to code again). One use case, one method, start to finish with no wussy subroutines baby!
Many people say that Ruby is like a developer magnifier that allows good developers to be faster and bad developers to fail faster. That might be so, but to me, Fortran 77 was more like an equalizer. Everybody is humbled before the “unknown error at line 0″ compiler message.
A computer without COBOL and FORTRAN is like a piece of chocolate cake without ketchup or mustard. (John Krueger)
The tree large enough that a stake capable of killing COBOL could be fashioned from its trunk has not yet grown anywhere upon the face of this verdant planet. (Dan Martinez)
Cobol has almost no fervent enthusiasts. As a programming tool, it has roughly the sex appeal of a wrench. (Charles Petzold)
Same site, other pages
Lisp has all the visual appeal of oatmeal with fingernail clippings mixed in. (((Larry Wall)))
If Java had true garbage collection, most programs would delete themselves upon execution. (Robert Sewell)
Using Java for serious jobs is like trying to take the skin off a rice pudding wearing boxing gloves. (Tel Hudson)
Perl: The only language that looks the same before and after RSA encryption. (Keith Bostic)